This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jhylton
Recipients jhylton, novalis_dt
Date 2008-11-24.17:55:21
SpamBayes Score 0.00043974342
Marked as misclassified No
Message-id <e8bf7a530811240955r1b2c81d8w1c5b7bee51b6d12e@mail.gmail.com>
In-reply-to <1227549003.47.0.321555177877.issue4327@psf.upfronthosting.co.za>
Content
I haven't thought about the code in a while, but what code that
modifies the AST are we worried about?  There are lots of
modifications in ast.c, since it is being created there.  The case we
really care about is sequences, where we want to modify the sequence.
The creation goes through macros like asdl_seq_SET(), so we could just
change the macro.  What are other cases we need to worry about?

Jeremy

On Mon, Nov 24, 2008 at 12:50 PM, David Turner <report@bugs.python.org> wrote:
>
> David Turner <novalis@novalis.org> added the comment:
>
> Sure, but that's an even bigger change.  Every piece of code which
> modifies the AST would now also have to modify parent pointers.  Having
> the pointers would make many things easier, but I didn't want to make a
> very invasive change like that without thinking it through thoroughly.
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue4327>
> _______________________________________
>
History
Date User Action Args
2008-11-24 17:55:23jhyltonsetrecipients: + jhylton, novalis_dt
2008-11-24 17:55:22jhyltonlinkissue4327 messages
2008-11-24 17:55:22jhyltoncreate