[docs] [issue13821] misleading return from isidentifier
R. David Murray
report at bugs.python.org
Thu Jun 29 10:21:06 EDT 2017
R. David Murray added the comment:
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.)
----------
nosy: +r.david.murray
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13821>
_______________________________________
More information about the docs
mailing list