Re: proposal: bring nonlocal to py2.x

From	Robin Becker <robin@reportlab.com>
Subject	Re: proposal: bring nonlocal to py2.x
Date	2014-01-15 12:07 +0000
References	<lb0ua4$fmj$1@ger.gmane.org> <CAFYqXL9UTE-2tMpUO313rKgt8vaH1UVnMA=RieuNTHUUUbW2Aw@mail.gmail.com> <lb10e5$d1i$1@ger.gmane.org> <CAPTjJmo_ZD1mMvikx8XjofgfwhDFZrbaXeM2q42-EKR1kFs-Jg@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.5502.1389787659.18130.python-list@python.org> (permalink)

Show all headers | View raw

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. :)
.......
fixing badly named variables is not a bug fix either, but that has happened in 
python 2.7. A micro change release changed

compiler.consts.SC_GLOBAL_EXPLICT

to

compiler.consts.SC_GLOBAL_EXPLICIT

this is a change of api for the consts module (if you regard exported variables 
as part of its api), but that didn't count for the developers.
-- 
Robin Becker

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: proposal: bring nonlocal to py2.x Robin Becker <robin@reportlab.com> - 2014-01-15 12:07 +0000

csiph-web