On Mon, Nov 2, 2009 at 10:06 AM, Raymond Hettinger <python at rcn.com> wrote: > > [Guido van Rossum] >> >> I'm -0 on backporting nonlocal to 2.7. I could be +0 if we added "from >> __future__ import nonlocal_keyword" (or some such phrasing) to enable >> it. > > With the "from __future__" option, what keeps you from being > a full +1 on nonlocal? Is there something that makes it a better > solution for 3.x than 2.x? Just curious about the pros and cons > from your point of view. I think the number of projects that can afford to drop support for 2.6 is pretty limited, so I think the utility of the feature is thereby also limited. -- --Guido van Rossum (python.org/~guido)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4