Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

memory, for example.) I remember previous discussions also referring to spelling this as outer which IMO passes #2 as well as the other, although arguably #4 is subjective ;-).-Almann -- Almann T. Goo[EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev

Re: [Python-Dev] Explicit Lexical Scoping (pre-PEP?)

with different spellings of local variables, then I would be +0 for it. Best Regards,Almann-- Almann T. Goo[EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http

Re: [Python-Dev] Lexical scoping in Python 3k

this gets brought up now and again. Best regards,Almann-- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive

Re: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)

obscure. I especially don't want to add an issue that is similar to one that PEP 227 went out of its way to avoid. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python

Re: [Python-Dev] PEP for Better Control of Nested Lexical Scopes

be where global was used in a closure where the name was shadowed in an enclosing scope. A from __future__ import lexical_global (which we'd have for adding the outer-like keyword anyway) could help diminish the growing pains. -Almann -- Almann T. Goo [EMAIL PROTECTED

Re: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)

of acceptable breakage in 3.0. You read my mind--I made a reply similar to this on another branch of this thread just minutes ago :). I am curious to see what the community thinks about this. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list

Re: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)

On 2/23/06, Steven Bethard [EMAIL PROTECTED] wrote: On 2/22/06, Almann T. Goo [EMAIL PROTECTED] wrote: def incrementer_getter(val): def incrementer(): val = 5 def inc(): ..val += 1 return val return inc

Re: [Python-Dev] Using and binding relative names (was Re: PEP for Better Control of Nested Lexical Scopes)

operator (i.e. :=) or an outer type keyword is stronger--the semantics in the language today are not adversely affected. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo

Re: [Python-Dev] PEP for Better Control of Nested Lexical Scopes

to to re-binding, which is probably a good thing) -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev

Re: [Python-Dev] PEP for Better Control of Nested Lexical Scopes

. Because of this, namespace objects have the potential to obfuscate things more than fix the language issue that I am addressing. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman

Re: [Python-Dev] PEP for Better Control of Nested Lexical Scopes

scope is not so. In a nutshell I am proposing a solution to make nested lexical scopes to be orthogonal with the global scope and removing a wart, as Jeremy put it, in the language. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list

[Python-Dev] PEP for Better Control of Nested Lexical Scopes

the community's opinion if there is enough out there that think this would be a worthwile endevour--or if there is already an initiative that I missed. Please let me know your questions, comments. Best Regards, Almann-- Almann T. Goo[EMAIL PROTECTED

Re: [Python-Dev] PEP for Better Control of Nested Lexical Scopes

of an argument against PEP 227 than what I am proposing. Again, today's Python already allows a developer to have deep nested scopes. -Almann -- Almann T. Goo [EMAIL PROTECTED] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org