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.

Author kbk
Recipients
Date 2006-07-28.19:44:32
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=149084

I don't mean to be derogatory by calling it a
hack!  Hacks can be very practical and useful, but
they are often not 100% reliable.  I'm only referring
to the port selection part of the patch.

Regarding REUSEADDR, if it is not set True there is
a timeout before the listening connection can be set
up again on the same socket.

As I recollect, it's ten sec, and so very annoying
when restarting IDLE especially during development.

Guido clued me in on REUSEADDR, which solved the 
problem.  According to the below links, it's only
operative when the socket is in the TIME_WAIT state,
and that should not be the case in the W2K overlapping
socket situation.

http://www.unixguide.net/network/socketfaq/4.5.shtml
http://www.unixguide.net/network/socketfaq/2.7.shtml

IDLE discussion should be on IDLE-dev unless it's 
something which affects the Python implementation or
changes the installation, i.e. how .py is bound on
Windows.
History
Date User Action Args
2007-08-23 15:43:01adminlinkissue1201569 messages
2007-08-23 15:43:01admincreate