Add UTR#39 discussion.
This commit is contained in:
parent
ae26a8cde2
commit
6986d93450
20
pep-3131.txt
20
pep-3131.txt
|
@ -120,10 +120,30 @@ The following changes will need to be made to the parser:
|
||||||
(such as pydoc) must be verified to continue to work when Unicode
|
(such as pydoc) must be verified to continue to work when Unicode
|
||||||
strings appear in ``__dict__`` slots as keys.
|
strings appear in ``__dict__`` slots as keys.
|
||||||
|
|
||||||
|
Open Issues
|
||||||
|
===========
|
||||||
|
|
||||||
|
John Nagle suggested consideration of Unicode Technical Standard #39,
|
||||||
|
[2]_, which discusses security mechanisms for Unicode identifiers.
|
||||||
|
It's not clear how that can precisely apply to this PEP; possible
|
||||||
|
consequences are
|
||||||
|
|
||||||
|
* warn about characters listed as "restricted" in xidmodifications.txt
|
||||||
|
* warn about identifiers using mixed scripts
|
||||||
|
* somehow perform Confusable Detection
|
||||||
|
|
||||||
|
In the latter two approaches, it's not clear how precisely the
|
||||||
|
algorithm should work. For mixed scripts, certain kinds of mixing
|
||||||
|
should probably allowed - are these the "Common" and "Inherited"
|
||||||
|
scripts mentioned in section 5? For Confusable Detection, it seems one
|
||||||
|
needs two identifiers to compare them for confusion - is it possible
|
||||||
|
to somehow apply it to a single identifier only, and warn?
|
||||||
|
|
||||||
References
|
References
|
||||||
==========
|
==========
|
||||||
|
|
||||||
.. [1] http://www.unicode.org/reports/tr31/
|
.. [1] http://www.unicode.org/reports/tr31/
|
||||||
|
.. [2] http://www.unicode.org/reports/tr39/
|
||||||
|
|
||||||
|
|
||||||
Copyright
|
Copyright
|
||||||
|
|
Loading…
Reference in New Issue