[Twisted-Python] _Win32Waker

Aron Bierbaum aronbierbaum at gmail.com
Mon Apr 20 19:16:39 EDT 2009


I have looked into this a little more and have noticed that if I
specify a port number instead of "0" it will always bind to the
correct "127.0.0.1" address. I still don't know why this only occurs
on certain Windows machines. I will hopefully get more time to look
into this in the next couple of days.

-Aron

On Mon, Mar 9, 2009 at 9:36 AM, Jean-Paul Calderone <exarkun at divmod.com> wrote:
> On Mon, 9 Mar 2009 09:17:14 -0500, Aron Bierbaum <aronbierbaum at gmail.com>
> wrote:
>>
>> I have been unable to reproduce this problem on multiple machines that
>> I have tested on. Also I have tried changing various network settings
>> on my machine without any change. Do you have any ideas what I should
>> be looking for?
>
> Not really, sorry.  I know that behavior often differs subtly or grossly
> from Windows machine to Windows machine, but not why.
>
> Jean-Paul
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>




More information about the Twisted-Python mailing list