Under Win98SE, if you say "from socket import *" at an
interactive python 2.0 prompt, you can see errorTab in
what dir() returns.
With a 2.1b1 interactive prompt, if you do the same
exact thing no errorTab is in the list. However, if
instead you say import socket and then dir(socket),
errorTab appears.
Not sure if this is a bug but it sure sent me on a
wild goose chase for a while. I don't think this is
correct Nested Scopes related behavior but I admit I
haven't fully understood this new feature.
This came up because I've been using the
timeoutsocket.py module from the Vaults of Parnassus
for a few weeks. It imports from socket. In a
different module I (very non-portably), then format an
nice error message based on the contents of errorTab.
This code now is broken under 2.1b1.
|