➜

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 SnoopJeDi
Recipients Carl.Friedrich.Bolz, Kodiologist, SnoopJeDi, eryksun, jack1142, serhiy.storchaka
Date 2022-02-01.00:41:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1643676078.45.0.911726926812.issue46555@roundup.psfhosted.org>
In-reply-to
Content 
> Why was it decided to not raise a syntax error...

I'm not sure if such a decision was even ever made, the error happens before normalization is applied. I.e. the parser is doing two things here: (1) validating the syntax against the grammar and (2) building the AST. Normalization happens after (1), and `𝕋𝕣𝕦𝕖 = 0` is valid syntax because the grammar is NOT defined in terms of normalized identifiers, it's describing the valid (but confusing!) assignment that Carl described.

I agree that this doesn't seem like bug, but it IS my new favorite quirk of identifier normalization.
History
Date User Action Args
2022-02-01 00:41:18SnoopJeDisetrecipients: + SnoopJeDi, Carl.Friedrich.Bolz, serhiy.storchaka, eryksun, Kodiologist, jack1142
2022-02-01 00:41:18SnoopJeDisetmessageid: <1643676078.45.0.911726926812.issue46555@roundup.psfhosted.org>
2022-02-01 00:41:18SnoopJeDilinkissue46555 messages
2022-02-01 00:41:18SnoopJeDicreate