This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: test_asyncore fix
Type: Stage:
Components: Tests Versions: Python 3.0
process
Status: closed Resolution: rejected
Dependencies: Superseder:
Assigned To: Nosy List: alanmcintyre, georg.brandl, hdiwan650
Priority: normal Keywords: patch

Created on 2007-08-05 07:10 by hdiwan650, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
test_asyncore_port.pat hdiwan650, 2007-08-05 07:10
Messages (4)
msg52991 - (view) Author: Hasan Diwan (hdiwan650) Date: 2007-08-05 07:10
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. 
msg52992 - (view) Author: Alan McIntyre (alanmcintyre) * (Python committer) Date: 2007-08-05 13:45
This change has already been made to test_asyncore.py as part of rev 56604 on July 28, 2007.
msg52993 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2007-08-05 14:33
Will it be backported to 2.5?
msg52994 - (view) Author: Alan McIntyre (alanmcintyre) * (Python committer) Date: 2007-08-05 15:04
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.
History
Date User Action Args
2022-04-11 14:56:25adminsetgithub: 45278
2008-01-06 22:29:45adminsetkeywords: - py3k
versions: + Python 3.0
2007-08-05 07:10:58hdiwan650create