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 pablogsal
Recipients aroberge, gvanrossum, lazka, lys.nikolaou, pablogsal
Date 2020-12-15.13:05:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608037506.44.0.443713247309.issue42577@roundup.psfhosted.org>
In-reply-to
Content
I concur, handling also multi-line constructs is tricky and I would prefer not to implement some hack for specific situations because my experience is that balancing that with other things Is tricky. As Lysandros mentioned, the parser reports correctly the location of the error as indentation is non important inside parentheses and the code there could be an expression or the begging of a generator.

On the other hand we could think if we have a way of detecting of a syntax error occurs in the context of an unclosed parentheses and maybe do something about it, but I have no idea still how many false negatives could appear.
History
Date User Action Args
2020-12-15 13:05:06pablogsalsetrecipients: + pablogsal, gvanrossum, aroberge, lazka, lys.nikolaou
2020-12-15 13:05:06pablogsalsetmessageid: <1608037506.44.0.443713247309.issue42577@roundup.psfhosted.org>
2020-12-15 13:05:06pablogsallinkissue42577 messages
2020-12-15 13:05:06pablogsalcreate