Message297270
IMO allow_non_nfkc=True that just returns False would be a bad idea, since as Benjamin points out it *is* a valid identifier, it's just not normalized (yet). Raising might work, that way you could tell the difference, but that would be a weird API for such a check function. Regardless, we should probably keep this issue to a doc patch, and open a new issue for any proposed enhancement request.
And you probably want to discuss it on python-ideas first, since the underlying issue is a bit complex and the solution non-obvious, with possible knock-on effects. (Or maybe I'm wrong and the consensus will be that returning False with that flag would be fine.) |
|
Date |
User |
Action |
Args |
2017-06-29 14:21:06 | r.david.murray | set | recipients:
+ r.david.murray, pitrou, vstinner, benjamin.peterson, ezio.melotti, docs@python, Jim.Jewett, serhiy.storchaka, mbussonn |
2017-06-29 14:21:06 | r.david.murray | set | messageid: <1498746066.3.0.805066782601.issue13821@psf.upfronthosting.co.za> |
2017-06-29 14:21:06 | r.david.murray | link | issue13821 messages |
2017-06-29 14:21:05 | r.david.murray | create | |
|