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 lys.nikolaou
Recipients aroberge, gvanrossum, lazka, lys.nikolaou, pablogsal
Date 2020-12-14.23:35:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for opening an issue here, Christoph. This is the right place to discuss this.

Indeed the parser is pretty dumb when reporting errors. In the technical sense the colon is the right thing to point to, since it's the first token that's not grammatically correct. Of course, it's somewhat misleading that it points to a line that *seems* correct, but that probably as good as we can do with the parser's current error reporting mechanisms.

Showing more that one lines would indeed solve this specific case, but implementing this is also difficult and I don't think it's worth it for such an edge case.

Guido, Pablo, your views on this?
Date User Action Args
2020-12-14 23:35:53lys.nikolaousetrecipients: + lys.nikolaou, gvanrossum, aroberge, lazka, pablogsal
2020-12-14 23:35:53lys.nikolaousetmessageid: <>
2020-12-14 23:35:53lys.nikolaoulinkissue42577 messages
2020-12-14 23:35:53lys.nikolaoucreate