New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_asyncore fix #45278
Comments
Fixes the socket.error(48, 'address already in use') intermittent failure by binding to an arbitrary high port and then using getsockname() to retrieve the port. There is a further error with the socket.error module that I think I'd like some hours of sleep before looking at. |
This change has already been made to test_asyncore.py as part of rev 56604 on July 28, 2007. |
Will it be backported to 2.5? |
I don't know; I wouldn't mind doing it. Are there any special considerations for moving tests back to an older version? I can port the final set of changes to Py3k as well, since it seems that the discussion of this particular problem made its way over to the 3k mailing list at some point. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: