Xavier Morel added the comment:
> But if we allow for ellipsis, then would we not also have to start allowing
> characters like ≥ and ≤ in Python?
No, they're not defined as canonically equivalent to >= and <= by the Unicode
specification:
>>> unicodedata.normalize('NFKD', '…')
...
New submission from Xavier Morel xavier.mo...@masklinn.net:
In Python 3, ... became useable as a normal expression, and translates into
an ellipsis instance.
Unicode defines an ellipsis character … (U+2026 HORIZONTAL ELLIPSIS) which is
canonically equivalent to a 3-sequence of FULL STOP
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12056
___
___
Python-bugs-list
Brandon Craig Rhodes bran...@rhodesmill.org added the comment:
But if we allow for ellipsis, then would we not also have to start allowing
characters like ≥ and ≤ in Python? And the problem with any of these
(admittedly very attractive) substitutions is that they seem to abandon the
principle
Benjamin Peterson benja...@python.org added the comment:
Making such substitutions is a good way to introduce subtle bugs.
--
nosy: +benjamin.peterson
resolution: - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
