[wingide-users] I can't get debugging from inside of Wing to work
Jens at arena.net
Mon Dec 19 16:13:14 MST 2011
Thanks Stephan! Debugging from the Python Shell would be a nice addition to Wing, but knowing I need to have separate files or unit tests to make the debugger work clears up a lot for me!
Jens Hauch ] ArenaNet
Technical Art and FX Lead :: High altitude shader operator ~ All Around Nice Guy
From: Wingware Support [mailto:support at wingware.com]
Sent: Monday, December 19, 2011 1:12 PM
To: Jens Hauch
Cc: wingide-users at wingware.com
Subject: Re: [wingide-users] I can't get debugging from inside of Wing to work
On 12/19/11 2:57 PM, Jens Hauch wrote:
> To clarify, by special code, I mean adding this to the bottom of the module I am debugging:
> if __name__ == "__main__":
> if len(sys.argv)> 1:
> eval( sys.argv )()
> It would be nice if there was a way I didn't have to do that. BTW, I am new to debugging so am approaching this from a very naive standpoint.
Using unit tests to test the module is probably the preferred approach
here but another idea is to set a breakpoint on the last 'def' or
'class' in the file, debug to it, step over, and then use the Debug
Probe to test out the module.
Or, you can right click and Evaluate File in Python Shell and invoke
things in the same way.
Neither of these currently will stop at breakpoints, however. Using
unit tests would solve that problem.
Wingware | Python IDE
Advancing Software Development
More information about the wingide-users