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

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

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

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

[Jeremy]
> ...
> I think few of us would be interested in making frequent use of it
> to add all sorts of variant language features.  Rather, I imagine
> it would be used only -- or primarily -- to introduce new features
> that will become standard at some point.

In my view, __future__ is *only* for the latter.

Somebody who wants to write a PEP for an analogous scheme keying off, say,
__jerking_off__, is welcome to do so, but anything else would be a 2.2 PEP
at best.

from-__jerking_off__-import-curly_braces-ly y'rs  - tim

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