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
2007/7/30, Jean-Paul Calderone <[EMAIL PROTECTED]>:
> Uh, no, that's basically totally wrong. Details on the ticket.
I rejected it.
Regards,
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
Python-Dev mai
Hasan,
We made a change to bind the server to port 0, so that an unused port
is selected for each test. I wasn't able to reproduce the failure
after making this change; is the current trunk still failing for you?
Cheers,
Alan
On 7/30/07, Hasan Diwan <[EMAIL PROTECTED]> wrote:
> The issue seems
On Sun, 29 Jul 2007 23:40:29 -0700, Hasan Diwan <[EMAIL PROTECTED]> wrote:
>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 th
