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 methane
Recipients Mark.Shannon, benjamin.peterson, flherne, georg.brandl, lukasz.langa, methane, ned.deily, rhettinger, serhiy.storchaka, vstinner
Date 2018-04-13.04:58:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523595490.92.0.682650639539.issue32911@psf.upfronthosting.co.za>
In-reply-to
Content
> in practice `ast.parse()` is often used with smaller fragments of source code that don't directly correspond to a complete module, and this behaviour makes no sense in such cases.
>
> The resulting bug in kdev-python took a while to track down (because I had no immediate reason to suspect this change), and will be somewhat awkward to workaround.

Would you elaborate it more, please?
Without concrete example, we cannot to decide how it's important problem.

> I would prefer that this be reverted; it's likely to break a variety of users in strange ways.

I don't want to revert, see discussions in this issue and PR-5927.

And would you give us real world example of "variety of users"?
How many applications use ast.parse for such way?
History
Date User Action Args
2018-04-13 04:58:10methanesetrecipients: + methane, georg.brandl, rhettinger, vstinner, benjamin.peterson, ned.deily, lukasz.langa, Mark.Shannon, serhiy.storchaka, flherne
2018-04-13 04:58:10methanesetmessageid: <1523595490.92.0.682650639539.issue32911@psf.upfronthosting.co.za>
2018-04-13 04:58:10methanelinkissue32911 messages
2018-04-13 04:58:10methanecreate