[wingide-users] Anyone using Wing to write Django code
yarkot1 at gmail.com
Tue Jan 15 01:24:20 MST 2008
Neither one of these methods seems to work on my PC.
All I'm doing is running thru the basic 4 django tutorials from
I get a dialog saying "The Debug Process never connected back to WingIDE:
Aborting debug session."
Of course, the dialog refers me to " See Trouble-shooting Failure to Debug
in the users manual."
which I can find in the index, but from the Manual PDF I get this dialog
when trying to "go to" this seciton:
"The specified file #trouble-shooting-failure-to-debug.pdf does not
(Windows XP; Python 2.5.1)
On Jan 11, 2008 2:11 PM, Jacob Lundqvist <jacob.lundqvist at gmail.com> wrote:
> 11 jan 2008 kl. 16.31 skrev Wingware Support:
> > Michael Hipp wrote:
> >> Anyone here using Wing to write and debug Django framework code?
> >> Any special tricks or gotchas?
> >> I've been using Wing for a while but just getting started with
> >> Django.
> > Some tips are collected here:
> > http://wingware.com/doc/howtos/django
> There is another method, wich at least I find more convinient, keeping
> the django reload-on-save magic.
> What I do is to put a link to wingdbstub.py in my top django dir
> (where manage.py is located)
> ln -s /usr/lib/wingide3.0/wingdbstub.py
> you could off course copy wingdbstub.py to this place, but then you
> have to copy it again each time wing is updated, sucks especially
> during beta periods ;)
> Next make sure you have enabled passive listen (the little bugg in
> bottom left)
> Then in your code just put a: import wingdbstub
> in files you want do debug and set breakpoints as usual
> This way if you change something, just save - django restarts and
> reguest the page in your browser again.
> regards /Jacob Lundqvist
> Wing IDE users list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wingide-users