In Wing 101 the standard output (e,g. from print) from a program is sent to the Python Shell panel, except when starting step debugging, in that case it is sent to Debug I/O panel. I Wing Personal, the standard output seem to be sent always to the Debug I/O panel. Do you confirm? What is the reason for this different behaviour?
Wing Personal and Wing Pro run programs in the debugger by default. You can get the Wing 101 behavior of evaluating a file in the Python Shell by using the evaluate-file-in-shell command. The reason for the difference is the the folks who helped with the original design of Wing 101 wanted to introduce the shell before the debugger.
Thanks for confirming and clarifying this. I would be more interested in a way to get the Wing Personal/Pro behaviour inside Wing 101, since for less expert people seems to be easier to understand and also more uniform across the 3 Wing versions. Why not a flag in Wing 101 to use the Debug I/O by default ?
In Wing 101, just use the bug icon in the toolbar to start the debugger to get the same behavior in Wing Personal and Pro. Note that difference is whether the debugger is used or not -- where the output is seen is a consequence of that. Wing 101 is designed to be use in introductory courses (e.g. CS 101) so it's intentionally different than Personal and Pro. Note that courses also have the option of using Personal or Pro if they want to use a IDE with more features.
Comments