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 CCLDArjun, lys.nikolaou, pablogsal
Date 2021-06-06.23:57:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623023830.0.0.821178379845.issue44324@roundup.psfhosted.org>
In-reply-to
Content
>  I saw that unclosed parentheses' special error are checked in the same place. 

Just to clarify: unclosed parentheses is a tokenizer error, not a parser error and this is handled by checking the tokenize status when it has already failed. The reason is done after the failed parser is because our tokenizer is made lazy and to check for unclosed pantheses you need to fully parse everything, and this needs a driver. There is no semantic analysis here, just checking the lexer status: that's why is handled separately
History
Date User Action Args
2021-06-06 23:57:10pablogsalsetrecipients: + pablogsal, lys.nikolaou, CCLDArjun
2021-06-06 23:57:10pablogsalsetmessageid: <1623023830.0.0.821178379845.issue44324@roundup.psfhosted.org>
2021-06-06 23:57:09pablogsallinkissue44324 messages
2021-06-06 23:57:09pablogsalcreate