James Hutchison added the comment:
That makes no sense. Why does:
s = socket.socket()
s.bind(('',50007))
s.listen(1);
s.close();
fix the issue then?
Re-opening, this issue should be understood because having such an operation
randomly fail is unacceptable for a production system. How does python choose a
port to open a connection on? If windows reports the wrong error then shouldn't
python try a different port number anyways (considering I have no control over
what port Python chooses to open a connection on)?
----------
status: closed -> open
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue15779>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
