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/2003-October/039676.html below:

[Python-Dev] Let's table the discussion of replacing 'global'

[Python-Dev] Let's table the discussion of replacing 'global'Brett C. bac at OCF.Berkeley.EDU
Mon Oct 27 21:41:48 EST 2003
Jeremy Hylton wrote:

> On Mon, 2003-10-27 at 12:29, Guido van Rossum wrote:
> 
>>>I'm going to make a suggestion.  Let's shelve this topic for the time being
>>>and simply summarize the issues in an informational PEP aimed at
>>>Py3k.
>>
>>Great idea.  I'm getting tired of it too; Alex and I don't seem to be
>>getting an inch closer to each other.
>>
>>
>>>We don't even know (at least I don't) if we want an implicit search
>>>for outer scope variables or an explicit specification of which
>>>scope such variables should be defined in.  If, for some reason,
>>>nested scopes make a quick exit in Py3k, this would all be moot
>>>anyway.
>>
>>Sorry to disappoint you, but nested scopes aren't going away.
> 
> 
> I haven't had time to participate in this thread -- too much real work
> for the last several days -- but I'd be happy to write a PEP that
> summarizes the issues.
> 

Woohoo!  PEPs for generator expressions, copying iterators, and now 
'global' "stuff"!  This will make summarizing the 700-odd emails I have 
for the next summary (at this point; the thing grows an average of 50 
emails a day as of late) a *heck* of a lot easier.  Thanks Jeremy, 
Raymond, and Alex.

-Brett


More information about the Python-Dev mailing list

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