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 serhiy.storchaka
Recipients Anthony Sottile, Carl.Friedrich.Bolz, Joshua.Landau, alimuldal, gvanrossum, nedbat, pablogsal, rrauenza, sco1, serhiy.storchaka, shreyanavigyan, steve.dower
Date 2021-04-18.15:25:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
PR 25466 makes the tokenizer emitting a deprecation warning if the numeric literal is followed by one of keywords which are valid after numeric literals. In future releases it will be changed to syntax warning, and finally to syntax error.

It is breaking change, because it makes invalid currently allowed syntax like `0 in x` or `1or x` (but `0or x` is already error).

See also issue21642 which allowed parsing "1else" as "1 else". Not all were agreed with that fix.

Perhaps we need to rewrite also some paragraphs in the language specification.
Date User Action Args
2021-04-18 15:25:14serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, Carl.Friedrich.Bolz, nedbat, Joshua.Landau, steve.dower, Anthony Sottile, pablogsal, sco1, shreyanavigyan, alimuldal, rrauenza
2021-04-18 15:25:14serhiy.storchakasetmessageid: <>
2021-04-18 15:25:14serhiy.storchakalinkissue43833 messages
2021-04-18 15:25:14serhiy.storchakacreate