[issue4397] test_socket fails occassionaly in teardown: AssertionError: [Errno 57] Socket is not connected

Mark Dickinson report at bugs.python.org
Thu Jan 15 15:01:47 CET 2009


Mark Dickinson <dickinsm at gmail.com> added the comment:

Hmm.  I take it back:  this *does* appear to be OS X specific.
I've attached a small (17-line) example that fails with
the Errno 57 error on OS X, but passes on the Linux machines I tested.

In this example, it appears that when 'conn.close()' is called by the 
server, the client socket 'cli' is automatically disconnected, hence
the shutdown failure.  On Linux that doesn't happen.

Can anyone shed any light on this, and/or suggest what should be done?

----------
components: +Macintosh
stage: patch review -> 
Added file: http://bugs.python.org/file12752/socket_bug.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4397>
_______________________________________


More information about the Python-bugs-list mailing list