Re: [Python-Dev] Unbound locals in class scopes

2015-06-21 Thread Nick Coghlan
On 22 June 2015 at 08:46, Ivan Levkivskyi wrote: > > > On 21 June 2015 at 22:05, Guido van Rossum wrote: >> >> On Sun, Jun 21, 2015 at 6:22 PM, Ivan Levkivskyi >> wrote: >>> >>> It is still not clear whether Guido's comment still stands for not >>> raising an UnboundLocalError in class definitio

Re: [Python-Dev] Unbound locals in class scopes

2015-06-21 Thread Ivan Levkivskyi
On 21 June 2015 at 22:05, Guido van Rossum wrote: > > On Sun, Jun 21, 2015 at 6:22 PM, Ivan Levkivskyi wrote: >> >> It is still not clear whether Guido's comment still stands for not raising an UnboundLocalError in class definitions but using globals instead. > > > Can you phrase this in the form

Re: [Python-Dev] Unbound locals in class scopes

2015-06-21 Thread Guido van Rossum
On Sun, Jun 21, 2015 at 6:22 PM, Ivan Levkivskyi wrote: > It is still not clear whether Guido's comment still stands for not raising > an UnboundLocalError in class definitions but using globals instead. > Can you phrase this in the form of an example, showing what it currently does and what you

Re: [Python-Dev] Unbound locals in class scopes

2015-06-21 Thread Ivan Levkivskyi
On 20 June 2015 at 18:39, Ron Adam wrote: > > > On 06/20/2015 12:12 PM, Ron Adam wrote: > >> >> >> On 06/20/2015 02:51 AM, Ivan Levkivskyi wrote: >> > > Guido said 13 years ago that this behavior should not be changed: >>> https://mail.python.org/pipermail/python-dev/2002-April/023428.html, >>>

Re: [Python-Dev] PEP 490: Chain exceptions at C level

2015-06-21 Thread Antoine Pitrou
On Sat, 20 Jun 2015 21:16:48 +0200 "M.-A. Lemburg" wrote: > On 20.06.2015 09:30, Victor Stinner wrote: > > Hi, > > > > I didn't get much feedback on this PEP. Since the Python 3.6 branch is > > open (default), it's probably better to push such change in the > > beginning of the 3.6 cycle, to catc

Re: [Python-Dev] async __setitem__

2015-06-21 Thread Guido van Rossum
On Sun, Jun 21, 2015 at 12:48 AM, Greg Ewing wrote: > Nick Coghlan wrote: > >> What if we're assigning to >> multiple targets, do the run in parallel? How is tuple unpacking >> handled? How is augmented assignment handled? >> >> If we allow asynchronous assignment, do we allow asynchronous deleti