proposal: bring nonlocal to py2.x
Robin Becker
robin at reportlab.com
Wed Jan 15 07:07:25 EST 2014
More information about the Python-list mailing list
Wed Jan 15 07:07:25 EST 2014
- Previous message (by thread): proposal: bring nonlocal to py2.x
- Next message (by thread): proposal: bring nonlocal to py2.x
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message (by thread): proposal: bring nonlocal to py2.x
- Next message (by thread): proposal: bring nonlocal to py2.x
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list