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 steven.daprano
Recipients Maxime Belanger, ezio.melotti, steven.daprano, vstinner
Date 2017-12-12.12:25:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513081508.61.0.213398074469.issue32285@psf.upfronthosting.co.za>
In-reply-to
Content
Python 2.7 is in feature freeze, so this can only go into 3.7.

I would find this useful, and would like this feature. However, I'm concerned by your comment that you fall back on creating a normalized copy and comparing. That could be expensive, and shouldn't be needed. According to here:

http://unicode.org/reports/tr15/#Detecting_Normalization_Forms

in the worst case, you can incrementally check only the code points in doubt (around the "MAYBE" code points).
History
Date User Action Args
2017-12-12 12:25:08steven.dapranosetrecipients: + steven.daprano, vstinner, ezio.melotti, Maxime Belanger
2017-12-12 12:25:08steven.dapranosetmessageid: <1513081508.61.0.213398074469.issue32285@psf.upfronthosting.co.za>
2017-12-12 12:25:08steven.dapranolinkissue32285 messages
2017-12-12 12:25:08steven.dapranocreate