Nested scopes resolution -- you can breathe again!

[Robin Becker]

In article <mailman.982897324.9109.python-list at python.org>, Guido van
Rossum <guido at digicool.com> writes
.....
>We have clearly underestimated how much code the nested scopes would
>break, but more importantly we have underestimated how much value our
>community places on stability.  At the same time we really like nested
>scopes, and we would like to see the feature introduced at some point.
>
>So here's the deal: we'll make nested scopes an optional feature in
>2.1, default off, selectable on a per-module basis using a mechanism
>that's slightly hackish but is guaranteed to be safe.  (See below.)
>
....
The problem here is that of stability; introducing new versions which
break old extensions at the rate of two a year is the problem. Does this
2.1 release make all the changes to the API which are needed and if so
why do we need to turn python21.dll into python22.dll. The unixers might
get away with smart loaders, but win32 will require a complete rebuild
for all .pyds. The confusion caused by multiple versions is an issue. I
would prefer it if 2.1 moved to 2.11 instead of 2.2.

Whilst helping my colleague migrate from 1.5.2 to 2.0 we came up against
the dreaded python15.dll not found message. The irritating thing about
the message is that it didn't tell us which .pyd it was attempting to
load.
-- 
Robin Becker