Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #63972 > unrolled thread

Re: proposal: bring nonlocal to py2.x

Started byRobin Becker <robin@reportlab.com>
First post2014-01-15 12:07 +0000
Last post2014-01-15 12:07 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#63972 — Re: proposal: bring nonlocal to py2.x

FromRobin Becker <robin@reportlab.com>
Date2014-01-15 12:07 +0000
SubjectRe: proposal: bring nonlocal to py2.x
Message-ID<mailman.5502.1389787659.18130.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web