On 12/4/19 3:11 AM, Serhiy Storchaka wrote:
04.12.19 04:41, Ned Batchelder пише:
On 12/3/19 8:13 PM, Inada Naoki wrote:
I think it is too early to determine when to remove it.
Even only talking about it causes blaming war.
Has anyone yet given a reason to remove it? It will change working
code into broken code. Why do that?
Why the "<>" operator and the "L" suffix was removed?
Is this a serious question? Many things were removed in moving from
Python 2 to Python 3. It was explicitly decided that 2->3 would contain
breaking changes. If you recall, this caused a large amount of
controversy. Why bring that on ourselves again?
Maybe I missed something. Python used to pride itself on keeping old
code working. When hash randomization was introduced, it was decided to
be off by default in Python 2 because even though people shouldn't have
counted on the order of dicts, they were counting on it, and turning on
hash randomization would break code. So there we decided to keep things
insecure because otherwise code would break, even "wrong" code.
Now just because "it isn't needed anymore" we're going to break working
code? I don't understand the shift in philosophy.
--Ned.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/OGM2SHWH6ZJ434YVHGX2DXTG3HHSUZ6U/
Code of Conduct: http://python.org/psf/codeofconduct/
