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, terry.reedy
Date 2010-12-25.15:19:15
SpamBayes Score 5.7232e-14
Marked as misclassified No
Message-id <AANLkTi=1v2x_4pKqx-mZFJvXiOWgvWyE3uGQXPh6zy9d@mail.gmail.com>
In-reply-to <1293288238.01.0.93876038413.issue10769@psf.upfronthosting.co.za>
Content
2010/12/25 Sven Brauch <report@bugs.python.org>:
>
> Sven Brauch <svenbrauch@googlemail.com> added the comment:
>
> Well, weather it's supposed to or not, it *does* contain the line number information:
> <ExprAst lineno="1" col_offset="0">
> For your example, the AST for "foo" tells you the offset for foo. If you want to know the offset (well, "offset") for blah, why not look at foo? Currently, the information is just copied from foo to blah.

What if it's like this, though?

x = (    foo).blah

>
> Anyway, I'd like to get away from this abstract discussion which is not likely to yield a result... is there any reason not to do it like I suggested other than the philosophical "it's wrong"? Or don't you agree that the information given this way would be more useful?

It wouldn't be any more useful than it is now. I don't think it's
reasonably possible to preserve every last obscure formatting in ast.
History
Date User Action Args
2010-12-25 15:19:17benjamin.petersonsetrecipients: + benjamin.peterson, georg.brandl, rhettinger, terry.reedy, scummos
2010-12-25 15:19:16benjamin.petersonlinkissue10769 messages
2010-12-25 15:19:15benjamin.petersoncreate