This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: 2.1b1 from socket import* omits errorTab
Type: Stage:
Components: Interpreter Core Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: skip.montanaro Nosy List: esasaki, moshez, skip.montanaro
Priority: normal Keywords:

Created on 2001-03-07 09:40 by esasaki, last changed 2022-04-10 16:03 by admin. This issue is now closed.

Messages (3)
msg3762 - (view) Author: Ernie Sasaki (esasaki) Date: 2001-03-07 09:40
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.
msg3763 - (view) Author: Moshe Zadka (moshez) (Python triager) Date: 2001-03-18 11:57
Logged In: YES 
user_id=11645

For the record, it seems to me that he's right. errorTab
is *not* used inside socket.py, so it *must* be defined
so that other people can use it, whether it is documented or
not.
msg3764 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2001-03-18 19:54
Logged In: YES 
user_id=44345

taken care of.  just an oversight on my part.
History
Date User Action Args
2022-04-10 16:03:50adminsetgithub: 34112
2001-03-07 09:40:53esasakicreate