On 7/02/21 9:58 am, Steve Holden wrote:
My suggestion that it be introduced via __future__ due to its contentious nature met immediate resistance.
__future__ is for things that are changing in incompatible ways. This is an entirely new feature that doesn't conflict with anything existing, so it doesn't need __future__. -- Greg _______________________________________________ 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/T3CJQWO7DQEJPECHUYJH655D75LMVOVM/ Code of Conduct: http://python.org/psf/codeofconduct/
