On Sat, Feb 6, 2021 at 9:34 PM Greg Ewing <greg.ew...@canterbury.ac.nz> wrote: > __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__.
The initial pattern matching syntax and semantics with its many corner cases may be incompatible with a future way of doing pattern matching that is better. Best, Luciano > > -- > 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/ -- Luciano Ramalho | Author of Fluent Python (O'Reilly, 2015) | http://shop.oreilly.com/product/0636920032519.do | Technical Principal at ThoughtWorks | Twitter: @ramalhoorg _______________________________________________ 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/QDOY4PN6MC5KPGWM5Z6TAWQUPFVSEYIQ/ Code of Conduct: http://python.org/psf/codeofconduct/
