On 2022-03-24 10:43, Andrew Svetlov wrote:
The proposal doesn't work well with type hints: atuple(a=1, b=2) and
atuple(a="a", b="b") generates the same type.
I'm neither here nor there on the original proposal, but I just want to
push back against this reasoning. Type hints are an entirely optional
feature of Python which do not affect the runtime behavior of Python
code in any way (except insofar as other code explicitly reads the
annotations), and this has been explicitly reiterated multiple times
(e.g., in PEPs). In my view, how something interacts with typing has no
relevance in evaluating a proposal such as this. To allow typing
considerations to constrain Python's future development in any way
whatsoever is to slide down the slippery slope which was explicitly
disavowed in PEP 484, namely a gradual move towards a de facto
"requirement" for static typing. I would most heartily prefer to avoid
that.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at
https://mail.python.org/archives/list/python-ideas@python.org/message/L67XX3TUEOFNLL4EJ56SX4UQAAV3TOU5/
Code of Conduct: http://python.org/psf/codeofconduct/
