Re: proposal: bring nonlocal to py2.x

2014-01-15 Thread Terry Reedy
On 1/15/2014 7:07 AM, Robin Becker wrote: On 13/01/2014 15:28, Chris Angelico wrote: .. It's even worse than that, because adding 'nonlocal' is not a bugfix. So to be committed to the repo, it has to be approved for either 2.7 branch (which is in bugfix-only maintenance mode) or 2.8 bra

Re: proposal: bring nonlocal to py2.x

2014-01-15 Thread Chris Angelico
On Wed, Jan 15, 2014 at 11:07 PM, Robin Becker wrote: > On 13/01/2014 15:28, Chris Angelico wrote: > .. > >> >> It's even worse than that, because adding 'nonlocal' is not a bugfix. >> So to be committed to the repo, it has to be approved for either 2.7 >> branch (which is in bugfix-only m

Re: proposal: bring nonlocal to py2.x

2014-01-15 Thread Robin Becker
On 13/01/2014 15:28, Chris Angelico wrote: .. It's even worse than that, because adding 'nonlocal' is not a bugfix. So to be committed to the repo, it has to be approved for either 2.7 branch (which is in bugfix-only maintenance mode) or 2.8 branch (which does not exist). Good luck. :)

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Terry Reedy
On 1/13/2014 9:47 AM, Neal Becker wrote: py3 includes a fairly compelling feature: nonlocal keywork [keyword] But backward compatibility is lost. I am not sure what your particular point is. Every new feature, in any release, if used, makes code not compatible with earlier releases that do

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Chris Angelico
On Tue, Jan 14, 2014 at 2:24 AM, Mark Lawrence wrote: > But it could theoretically happen if Neal wants it so badly that he raises > an issue on the bug tracker against Python 2.7, finds all the relevant > source code in Python 3, back ports it, modifies all the relevant docs and > unit tests, the

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Mark Lawrence
On 13/01/2014 15:28, Chris Angelico wrote: On Tue, Jan 14, 2014 at 2:24 AM, Mark Lawrence wrote: But it could theoretically happen if Neal wants it so badly that he raises an issue on the bug tracker against Python 2.7, finds all the relevant source code in Python 3, back ports it, modifies all

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Mark Lawrence
On 13/01/2014 15:12, Giampaolo Rodola' wrote: On Mon, Jan 13, 2014 at 3:47 PM, Neal Becker mailto:ndbeck...@gmail.com>> wrote: py3 includes a fairly compelling feature: nonlocal keywork But backward compatibility is lost. It would be very helpful if this was available on py2.x. It

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Chris Angelico
On Tue, Jan 14, 2014 at 1:47 AM, Neal Becker wrote: > py3 includes a fairly compelling feature: nonlocal keywork > But backward compatibility is lost. It would be very helpful > if this was available on py2.x. Python 2.x is no longer being developed. It won't be gaining features like this. Use t

Re: proposal: bring nonlocal to py2.x

2014-01-13 Thread Giampaolo Rodola'
On Mon, Jan 13, 2014 at 3:47 PM, Neal Becker wrote: > py3 includes a fairly compelling feature: nonlocal keywork > But backward compatibility is lost. It would be very helpful > if this was available on py2.x. > > -- > https://mail.python.org/mailman/listinfo/python-list > It's not gonna happe

proposal: bring nonlocal to py2.x

2014-01-13 Thread Neal Becker
py3 includes a fairly compelling feature: nonlocal keywork But backward compatibility is lost. It would be very helpful if this was available on py2.x. -- https://mail.python.org/mailman/listinfo/python-list