Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2001-March/013322.html below:

an alternative to the __future__ syntax

• Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Objects funcobject.c,2.35,2.36
• Next message: [Python-Dev] PEP 236: an alternative to the __future__ syntax
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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

• Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Objects funcobject.c,2.35,2.36
• Next message: [Python-Dev] PEP 236: an alternative to the __future__ syntax
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4