On Jan 6, 11:46 am, Rob Williscroft wrote:
> Matimus wrote in news:2a3d6700-85f0-4861-84c9-9f269791f044
> Searching (AKA googling) for: nonlocal site:bugs.python.org
> leads to:http://bugs.python.org/issue4199
>
> Rob.
> --http://www.victim-prime.dsl.pipex.com/
Doh. I looked at the PEP and the 3
On Jan 6, 11:10 am, Matimus wrote:
> `nonlocal` should behave just like `global` does. It doesn't support
> that syntax either. So, yes it was intentional. No, there probably is
> no plan to support it in a later release.
>
> Matt
>From my perspective, that's an unfortunate decision and I questi
Matimus wrote in news:2a3d6700-85f0-4861-84c9-9f269791f044
@f40g2000pri.googlegroups.com in comp.lang.python:
> On Jan 6, 5:31 am, Casey wrote:
>> In PEP 3104 the nonlocal statement was proposed and accepted for
>> implementation in Python 3.0 for access to names in outer scopes. The
>> proposed
On Jan 6, 5:31 am, Casey wrote:
> In PEP 3104 the nonlocal statement was proposed and accepted for
> implementation in Python 3.0 for access to names in outer scopes. The
> proposed syntax included an optional assignment or augmented
> assignment to the outer name, such as:
>
> nonlocal x += 1
>
