Terry J. Reedy <[email protected]> added the comment:
I strongly disagree. '<>' is not a legal operator any more. It is a
parse-time syntax error. Whatever historical artifact is left in the CPython
tokenizer, recognizing '<>' is not exposed to Python code.
>>> p = ast.parse('a <> b')
Traceback (most recent call last):
...
a <> b
^
SyntaxError: invalid syntax
When '<>' was legal, we may presume that tokenizer recognized it, so that not
recognizing it was an intentional change. Reverting this would be a
dis-service to users.
I think that the PR and this issue should be closed. If the historical
artifact bothers you, propose removing it instead on introducing a bug into
tokenizer.
----------
nosy: +terry.reedy
type: -> enhancement
versions: -Python 3.9
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue42687>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
