[wingide-users] re-establishing Django/Wing debug connectivity

Wingware Support support at wingware.com
Thu Feb 11 07:07:28 MST 2010


Chris Curvey wrote:
> 
> 
> On Wed, Feb 10, 2010 at 1:46 PM, Wing IDE Support <support at wingware.com 
> <mailto:support at wingware.com>> wrote:
> 
>     On 2/10/10 12:12 PM, Chris Curvey wrote:
> 
>         But sometimes, Django gets stuck and I have to stop it with
>         Ctrl-Break.
>          (Control-C won't do it.)  Then I restart Django, and hit my webpage
>         again, but when I do, Django is never making the connection back to
>         Wing.  I can tell because my breakpoints are ignored, and the debug
>         toolbar doesn't change (debug button is enabled, stop button is
>         disabled).  The only way to re-enable the communication is to
>         stop both
>         Django and Wing, then restart both.
> 
> 
>     I suspect then issue is that Wing doesn't re-enable the passive
>     listening socket.  Could you try turning off passive listening and
>     then turn it back it on if this happens again?
> 
> 
> Yep, that's correct.  If I go into 
> Preferences->Debugger->External/Remote, then uncheck the box, hit apply, 
> check the box, hit OK, and restart my server, things go back to normal.

Note that an easier way to do this is to click on the bug icon in lower
left and uncheck/recheck passive listen there.  I'm not sure why it's
not re-enabling listen.  Sending an error log next time it gets into
this state may show us something.

-- 

Stephan Deibel
Wingware | Python IDE
Advancing Software Development

www.wingware.com


More information about the wingide-users mailing list