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 mbussonn
Recipients Jim.Jewett, benjamin.peterson, docs@python, ezio.melotti, mbussonn, pitrou, serhiy.storchaka, vstinner
Date 2017-06-24.05:48:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have been bitten by that as well. I think the doc should mention to verify that the given string is normalized, not that it **should** be normalized.

Agreed that If isidentifier could also possibly grow a `allow_non_nfkc=True` default parameter that would allow to deactivate internal normalisation and return False/Raise on Non NKFC that would be great. 

I'm also interested on having an option on ast.parse or compile to not normalize to at least be able to lint wether users are using non NFKC form, but that's another issue.

I'll see if I can come up with – at least – a documentation patch.
Date User Action Args
2017-06-24 05:48:27mbussonnsetrecipients: + mbussonn, pitrou, vstinner, benjamin.peterson, ezio.melotti, docs@python, Jim.Jewett, serhiy.storchaka
2017-06-24 05:48:27mbussonnsetmessageid: <>
2017-06-24 05:48:27mbussonnlinkissue13821 messages
2017-06-24 05:48:26mbussonncreate