Re: [Python-Dev] buildbot vs. Windows

2006-02-21 Thread Neal Norwitz
On 2/21/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Neal> IMO compiler warnings should generate emails from buildbot. > > > > It doesn't generate emails for any other condition. I think it should just > > turn the compilation section yellow. > > It would be

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

2006-02-21 Thread Greg Ewing
Terry Reedy wrote: > There were perhaps 10 > different proposals, including, I believe, 'outer'. Guido rejected them > all as having costs greater than the benefits. As far as I remember, Guido wasn't particularly opposed to the idea, but the discussion fizzled out after having failed to reach

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

2006-02-21 Thread Greg Ewing
Phillip J. Eby wrote: >def incrementer(val): >def inc(): >.val += 1 >return .val >return inc -1, too obscure. -- Greg ___ 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

2006-02-21 Thread Greg Ewing
Mark Russell wrote: > PEP 227 mentions using := as a rebinding operator, but rejects the > idea as it would encourage the use of closures. Well, anything that facilitates rebinding in outer scopes is going to encourage the use of closures, so I can't see that as being a reason to reject a parti

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

2006-02-21 Thread Greg Ewing
Just van Rossum wrote: > Btw, PJE's "crazy" idea (.name, to rebind an outer name) was proposed > before, but Guido wanted to reserve .name for a (Pascal-like) 'with' > statement. Hmm, I guess that doesn't apply any more, since we've already used "with" for something else. Regardless, names with

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

2006-02-21 Thread Almann T. Goo
> As far as I remember, Guido wasn't particularly opposed > to the idea, but the discussion fizzled out after having > failed to reach a consensus on an obviously right way > to go about it. My apologies for bringing this debated topic again to the front-lines--that said, I think there has been go

<    1   2