On Sun, Jul 03, 2005 at 03:30:17PM +0200, Reinhard Tartler wrote: > Debian sid has upgraded to twisted 2.0 and therefore I must support > it. I tried using londonlaw with the updated twisted version, but I > experienced the following bug: > > In the connections dialog, I enter the hostname of the server, and > press connect. Then nothings happens. (See attached screenshot). > Neither the client produces any message, nor the server receives a > connection request. When I press on "quit", the dialog closes as > expected, but the shell does not return from the command > "london-client". > > Entering the IP Adress however, the clients connects with the server, > and I can play the game (with the server using twisted 1.3.0!). > > So I assume that there is somethin wrong with resolving the hostname. > Now I wanted to hear your opinion, if this is a bug in londonlaw or a > regression in python-twisted, and how I should handle this bug.
Weird. I think the DNS resolution is getting interrupted due to some bad interaction with the wxPython main loop. I'll check on the Twisted mailing list to see if they can figure out what's going on. In the meantime, I just put out a 0.2.1 release which has a workaround. I just threw in an explicit call to socket.gethostbyname(), which seems to work fine. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
