On 8/4/07, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> Well, regardless of the brokenness of the patch, I do get two
> different failures from this test on OSX. The first is caused by
> trying to socket.bind() a port that's already been bound recently:
> That looks pretty easy to fix.
It was fix
On 04/08/07, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> Well, regardless of the brokenness of the patch, I do get two
> different failures from this test on OSX. The first is caused by
> trying to socket.bind() a port that's already been bound recently:
>
> Exception in thread Thread-2:
> Traceba
Well, regardless of the brokenness of the patch, I do get two
different failures from this test on OSX. The first is caused by
trying to socket.bind() a port that's already been bound recently:
Exception in thread Thread-2:
Traceback (most recent call last):
File "/Users/jyasskin/src/python/test
Hasan Diwan wrote:
> The issue seems to be in the socket.py close method. It needs to sleep
> socket.SO_REUSEADDR seconds before returning.
WHAT??? socket.SO_REUSEADDR is a flag that you pass when
creating a socket to tell it to re-use an existing address,
not something to be used as a timeout val
The issue seems to be in the socket.py close method. It needs to sleep
socket.SO_REUSEADDR seconds before returning. Yes, it is a simple fix
in python, but the socket code is C. I found some code in socket.py
and made the changes. Patch is available at
http://sourceforge.net/tracker/index.php?func=
