[Tutor] debugging a module from a Package with IDLE interpreter
D-Man
dsh8290@rit.edu
Wed, 4 Apr 2001 11:12:12 -0400
On Tue, Apr 03, 2001 at 03:50:25PM -0400, Benoit Dupire wrote:
| D-Man wrote:
...
| > Hmm, it must have been successfully imported before. I suppose the
| > following might work in your situation :
|
| Yep, that's my pb. The module was not successfully imported before.
|
...
| looks like a good idea...
| However it does not perform as wanted...
...
| I think the pb comes from IDLE...
Could be. If you aren't using any special features from IDLE (other
than the interactiveness, of course) then may I suggest using the
command line? If you are using windows, get cygwin. Bash is far
superior to DOS.
My technique tends to be one of using (g)vim to edit and an "xterm"
(ok, so I'm on windows too now, it's a DOS-term with cygwin) to
run/test. If it fails I can simply type "!![enter]" to execute the
command again. This is much easier and faster than hunting down idle
in the start menu and then setting it up again.
-D