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/013173.html below:

Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!)

Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!) Other situations like this (was RE: [Python-Dev] Nested scopes resolution -- you can breathe again!)Jeremy Hylton jeremy@alum.mit.edu
Fri, 23 Feb 2001 17:30:11 -0500 (EST)
Couple of issues the come to mind about __future__:

1 Should this work?

if x:
    from __future__ import nested_scopes

I presume not, but the sketch of the rules you posted earlier
presumably allow it.

2. How should the interactive interpreter be handled?

I presume if you type
>>> from __future__ import nested_scopes

That everything thereafter will be compiled with nested scopes.  This
ends up being a little tricky, because the interpreter has to hang
onto this information and tell the compiler about it.

Jeremy




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