[wingide-users] Here's a strangeone...SocketServer.ThreadingTCPServer

Harper, Jason jharper at qualcomm.com
Thu Apr 17 16:24:50 MDT 2008


Right...the in-line import of threading was being done in the thread I
spun up to run the server in.  Make sense.
Thanks.

-----Original Message-----
From: Wingware Support [mailto:support at wingware.com] 
Sent: Thursday, April 17, 2008 3:23 PM
To: Harper, Jason
Cc: wingide-users
Subject: Re: [wingide-users] Here's a
strangeone...SocketServer.ThreadingTCPServer

Harper, Jason wrote:
> I believe I have this one resolved.  The
SocketServer.ThreadingTCPServer
> object does an import of the threading module in its process_request
> method.  This seems to cause a problem with threading in general
> (outside of Wing).  I derived my own class from ThreadingTCPServer so
I
> can override the process_request method to avoid the in-line import of
> the threading module.

This makes a bit of sense, Wing imports threading when it starts the 
debugger so it can install needed hooks.  It's a good idea to do all 
imports in a single thread because there is an import lock in the 
interpreter internals that can cause problems.

Cheers,

John


More information about the wingide-users mailing list