In-Reply-To: <3F78AD93.1070906@alldunn.com>
> If you are single stepping through code and you have an error e.g.
> trying to access an attribute that doesn't exist, the target program
> just starts running again - debug finishes.
>
> If you're running outside Boa and the debugger the cmd window
> associated with the Python program shows an exception.
I guess Boa catches the stderr of the app it runs. Isn't there an
option to display that?
That seems to be the problem. It has a Traceback, Output and Errors
windows but doesn't show anything in them.
I'll raise this again in the Boa group. I think the author is away at the
moment.
Hugh
Hugh,
Have a look at this message - it looks like Riaan fixed it but it is not in the current release yet.
Read and respond to this message at: Boa Constructor - wxPython GUI Builder / Discussion / Open Discussion: Boa does not capture stderr/tb in debugger
By: riaan
Hi Keith,
I noticed this earlier as well, thanks for prodding me to action
Now fixed in my copy.
In Debugger.ChildProcessClient.ChildProcessClient.pollStreams, change:
stream = self.error_stream
Hugh Gibson wrote:
ยทยทยท
In-Reply-To: <3F78AD93.1070906@alldunn.com>
If you are single stepping through code and you have an error e.g. trying to access an attribute that doesn't exist, the target program just starts running again - debug finishes.
If you're running outside Boa and the debugger the cmd window associated with the Python program shows an exception.
I guess Boa catches the stderr of the app it runs. Isn't there an option to display that?
That seems to be the problem. It has a Traceback, Output and Errors windows but doesn't show anything in them.
I'll raise this again in the Boa group. I think the author is away at the moment.
Hugh
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org