Martin v. Löwis added the comment: As this is an error reported by Windows, it *very* unlikely is an issue with Python. Instead, it's a reaction that Windows produced to some sequence of events.
My guess is that another process had the address in use, apparently, Windows then reports WSAEACCESS in certain cases instead of the expected WSAEADDRINUSE. What specific socket operation was the one that failed? ---------- nosy: +loewis _______________________________________ 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
