socket timing problem
Timothy O'Malley
timo at alum.mit.edu
Sun Apr 22 21:27:05 EDT 2001
hola.
In article <uwv8fq8zu.fsf at ctwd0143.fitlinxx.com>, David Bolen <db3l at fitlinxx.com> wrote:
> Hmm - we're still having difficulties. For example, the accept()
> wrapper seems to return a native socket and not a TimeoutSocket.
Holy overlooking the obvious, Batman?
I'll fix that in version 1.15.
> We also seem to get a code 10022 but with why[1] set to "winsock
> error" rather than "Invalid argument" in the connect processing.
I can easily make changes to allow any 10022 error in connect(). I'll
throw that in version 1.15, too.
I'll post a new version with those two changes RSN (real soon now).
More information about the Python-list
mailing list