On Mon, Mar 28, 2022 at 4:44 PM Guido van Rossum <gu...@python.org> wrote:
> > "Future" imports are special to the parser, and they may also set a flag > for the runtime to alter its behavior, but they are intentionally not > treated specially by code generation, so they are still properly imported. > However the presence of the imported thing is not used by the runtime to > determine its behavior; those flags are stored elsewhere guided by the code > generator. > Right, this is why it's confusing when the object is there for no reason (the future import did not have any impact on the module, but the object showed up via an import *). > I don't think there's anything to do here. > How about the suggestion in https://bugs.python.org/issue26120 ? It's about these objects showing up in pydoc (both when the __future__ had an impact and when it didn't - in either case it's not an interesting part of the module's API).
_______________________________________________ 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/JVHTGPOZX72J73SUVKGEWBXHKK4KIFAV/ Code of Conduct: http://python.org/psf/codeofconduct/
