A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Nested scopes resolution -- you can breathe again!))

Draft PEP (RE: Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!)) Draft PEP (RE: Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!))Samuele Pedroni Samuele Pedroni <pedroni@inf.ethz.ch>
Mon, 26 Feb 2001 19:44:23 +0100 (MET)
Hi.

I have understood the point about making future feature inheritance
automatic ;)

So I imagine that the future features should at least end up being
visible as a (writeable?) code attribute:

co_futures or co_future_features

being a list of feature name strings.

or I'm wrong?

regards, Samuele Pedroni




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