Hello, On Sun, 7 Feb 2021 01:17:31 +0000 Paul Bryan <pbr...@anode.ca> wrote:
> On Sat, 2021-02-06 at 22:00 -0300, Luciano Ramalho wrote: > > > 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. > > That's not my understanding. My understanding is __future__ is meant > for features that potentially break existing code, and allows code to > opt-in in a release earlier than when it will behave that way by > default. From what I can tell with this PEP, existing code can > continue working the way it always has. And that's not understanding of the majority of Python users. For majority of "mere" users, __future__ is a marker that something new (and thus experimental, for these categories are again equivalent for most users) is being used in the current module. So, "from __future__ import with_statement" didn't mean to people "you can't use variable named 'with' in this module" (because majority of people never used such a variable name, so didn't care), but instead meant "this module uses the new 'with' statement, keep your ear sharp". And the current excuses go along the lines of "now that we've got a parser with exponential memory usage, we can use __future__ like... umm, never". Don't do that, keep using __future__ like it always was - to mark experimental features. > > Paul > -- 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/2O3ZSLNOKZABQD4FIX7KAGM6JSF7JFYC/ Code of Conduct: http://python.org/psf/codeofconduct/
