Message297270
| Author |
r.david.murray |
| Recipients |
Jim.Jewett, benjamin.peterson, docs@python, ezio.melotti, mbussonn, pitrou, r.david.murray, serhiy.storchaka, vstinner |
| Date |
2017年06月29日.14:21:05 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1498746066.3.0.805066782601.issue13821@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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.) |
|