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

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

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

• Previous message: Draft PEP (RE: Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!))
• Next message: [Python-Dev] editing FAQ?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Samuele Pedroni]
> 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?

I don't know.  Toward what end?  I expect that for beta1, none of the
automagic inheritance stuff will actually get implemented, and we're off to
the Python conference next week, so there's time to flesh out what the next
step *should* be.

• Previous message: Draft PEP (RE: Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!))
• Next message: [Python-Dev] editing FAQ?
• 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