On Sat, Feb 6, 2021 at 6:23 PM Chris Angelico <ros...@gmail.com> wrote: > How will a __future__ import help here? Are there syntactic or > behavioural changes that would be worth applying to some modules and > not others? The entire point of a __future__ import is to maintain > backward compatibility by, for instance, not introducing a keyword, > unless it is explicitly requested. What advantage would there be here?
The fact that a __future__ import only affects a single module is precisely the point: we may not want the feature in our code initially, but maybe we don't mind using third-party libraries that use it. A __future__ import would make clear to all that the feature is experimental, and maybe there could be __future__ imports for different parts of the proposal. > > AND it should be documented as provisional for several > > releases, like asyncio was (and remember: the asyncio API had lots of > > breaking changes and prompted the addition of the async/await > > keywords, a great improvement that forced the renaming of the very > > fundamental async function from the original API). > > Documenting as "provisional" means that its behaviour can change. > Again, how will that make things easier here? Telling everyone that the behaviour can change allows you to change the behaviour if you realize the behavior is unhelpful in some way. Again, that's just a huge feature and I believe we should consider one or more ways of making its adoption gradual and to make it easier to fix oversights if needed. Best, Luciano > ChrisA > _______________________________________________ > 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/VC3IV5XDTMKYZME75WQAHAEAWGOYTOBI/ > 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/OYXS7YTGJWI6S5VMQJD7A3STTF64DXBA/ Code of Conduct: http://python.org/psf/codeofconduct/
