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 benjamin.peterson
Recipients benjamin.peterson, georg.brandl, rhettinger, scummos
Date 2010-12-24.19:11:41
SpamBayes Score 7.988216e-05
Marked as misclassified No
Message-id <AANLkTi=p_V=2K6gzJmttqy-fN0OK7G4cMr8yr022coZP@mail.gmail.com>
In-reply-to <1293217373.29.0.750131610482.issue10769@psf.upfronthosting.co.za>
Content
2010/12/24 Raymond Hettinger <report@bugs.python.org>:
>
> Raymond Hettinger <rhettinger@users.sourceforge.net> added the comment:
>
> ISTM the whole point of an Abstract Syntax Tree is to express semantics while throwing away the syntax details.  The only reason any position information is kept is to support tracebacks and debugging.

I agree for the most part. It's also nearly impossible to preserve all
the detail one would want in an *abstract* syntax tree.

>
> Perhaps the OP's request should changed to "add function to concrete parse trees to show structure while preserving all the input detail returned by tokenize."

If someone can comment on what that would look like...
History
Date User Action Args
2010-12-24 19:11:44benjamin.petersonsetrecipients: + benjamin.peterson, georg.brandl, rhettinger, scummos
2010-12-24 19:11:41benjamin.petersonlinkissue10769 messages
2010-12-24 19:11:41benjamin.petersoncreate