Nick Coghlan wrote:
> Brett C. wrote:
>
>> OK, thanks to John Ehresman here at PyCon sprint I got logistix's
>> patch applied. Beyond a warning that a warning that decode_unicode()
>> is never called and the parser module failing to compile under Windows
>> everything should be fine for compiling
Brett C. wrote:
OK, thanks to John Ehresman here at PyCon sprint I got logistix's patch
applied. Beyond a warning that a warning that decode_unicode() is never
called and the parser module failing to compile under Windows everything
should be fine for compiling the AST branch.
Under Linux (Suse
Grant Olson wrote:
Make sure "AST" is used in the subject line; e.g., "[AST]" at
the beginning.
Unfortunately the AST group is only available for patches;
not listed for bug reports (don't know why; can this be fixed?).
Other than that, just assign it to me since I will most
likely be doin
Grant Olson wrote:
Make sure "AST" is used in the subject line; e.g., "[AST]" at
the beginning.
Unfortunately the AST group is only available for patches;
not listed for bug reports (don't know why; can this be fixed?).
Other than that, just assign it to me since I will most
likely be doin
> Make sure "AST" is used in the subject line; e.g., "[AST]" at
> the beginning.
> Unfortunately the AST group is only available for patches;
> not listed for bug reports (don't know why; can this be fixed?).
>
> Other than that, just assign it to me since I will most
> likely be doing AST
[Brett C.]
> Make sure "AST" is used in the subject line; e.g., "[AST]" at the beginning.
> Unfortunately the AST group is only available for patches; not listed for bug
> reports (don't know why; can this be fixed?).
Your wish is my command: there's an AST group in Python's bug tracker
now. FYI
Nick Coghlan wrote:
What's the current situation with providing fixes for AST branch problems?
Make sure "AST" is used in the subject line; e.g., "[AST]" at the beginning.
Unfortunately the AST group is only available for patches; not listed for bug
reports (don't know why; can this be fixed?).
What's the current situation with providing fixes for AST branch problems?
There's a simple one in parsenumber in Python/ast.c relating to int/long
unification and octal literals. The fix is just a direct copy of the relevant
code from parsenumber in the old compile.c.
Fixing it means the only f
