Hello, On Sun, 07 Feb 2021 13:32:17 +1300 Greg Ewing <greg.ew...@canterbury.ac.nz> wrote:
> 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__. We rented a time machine, went to the future (multiple plausible futures, as modern time machines allow, unlike the older crippled linear models, as shown in 1980is movies), saw that there were many good things missed, some requiring slightly incompatible changes, and decided to use __future__ right away. > -- > Greg -- Best regards, Paul mailto:pmis...@gmail.com _______________________________________________ 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/UTTMX7UISATDPFMXGIF7HMIEVF4HOOY7/ Code of Conduct: http://python.org/psf/codeofconduct/
