ScrIDE console output

A extensible, generic scripting IDE
Post Reply
Posts: 1
Joined: Thu Jul 29, 2004 6:08 pm
Location: Tokyo

ScrIDE console output

Post by Jim » Thu Aug 10, 2006 11:31 pm

The output in the ScrIDE console seems inconsistent on my 10.4.7 PPC machine, using the standard /usr/bin/python.

If I create a simple program like:
[code]print 1[/code]
and then run it with command-R, sometimes the Console shows '1', and sometimes it shows:

[code][Task /usr/bin/pythonw, pid=5368 launched]
&[GCC 3.3 20030304 (Apple Computer, Inc. build 1809)]
[Task exited status=0]

The first run is usually correct, and subsequent runs usually result in the latter... but it is not consistent.

Posts: 1464
Joined: Wed Feb 04, 2004 6:02 pm

Post by gandreas » Fri Aug 11, 2006 8:56 am

What you're seeing is the whole "debugger interaction dance", which, as you notice, you shouldn't see.

If you want, you can switch the debug mode to "None" (though obviously, you loose the ability to do things like debug exceptions and the like).

If you can figure out a way to consistently make this happen, please let me know so I can fix it (I've seen it myself, but only when I'm not trying to fix it).

Post Reply