PEP 236: an alternative to the __future__ syntax
but where's the patch?
Argh. It's now at http://www.informatik.hu-berlin.de/~loewis/python/directive.diff
other tools that parse Python will have to be adapted.
Yes, that's indeed a problem. Initially, that syntax will be used only to denote modules that use nested scopes, so those tools would have time to adjust.
The __future__ hack doesn't need that.
If it is *just* parsing, then yes. If it does any further analysis (e.g. "find definition (of a variable)" aka "find assignments to"), or if they inspect code objects, these tools again need to be adopted. Regards, Martin
Argh. It's now at http://www.informatik.hu-berlin.de/~loewis/python/directive.diff
other tools that parse Python will have to be adapted.
Yes, that's indeed a problem. Initially, that syntax will be used only to denote modules that use nested scopes, so those tools would have time to adjust.
The __future__ hack doesn't need that.
If it is *just* parsing, then yes. If it does any further analysis (e.g. "find definition (of a variable)" aka "find assignments to"), or if they inspect code objects, these tools again need to be adopted.
This is just too late for the first beta. But we'll consider it for beta 2! --Guido van Rossum (home page: http://www.python.org/~guido/)
participants (2)
-
Guido van Rossum
-
Martin v. Loewis