First time here? Check out the FAQ!
Ask Your Question
0

Traceback is printed to Debug I/O window after exception reported.

Debugger:Exception settings are 

Report Exceptions: When Printed
Report Logged Exceptions In When Printed Mode: True

In my exception handler I am logging the exception with logging.exception(...) so the debugger stops at the logging statement (as expected) and the logging output has been displayed in the Debug I/O window. The Exceptions toolbox window also shows a stack trace which is navigable by clicking (really nice by the way).The problem is that when I continue another stack trace is printed to the Debug I/O window. This behavior is different than what I would see on stderr when running the code from a console.

Behavior remains even if I ignore this exception location from the Exceptions tool.Wing version 5.1.12 (I plan on upgrading soon)Python 2.7.14Windows 10

Thanks

Max Slimmer's avatar
21
Max Slimmer
asked 2018-05-19 12:04:00 -0500
Wingware Support's avatar
3.9k
Wingware Support
updated 2020-01-22 19:56:19 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

2 Answers

0

It was mostly an annoyance while debugging but its awesome that it turned up a more significant issue. Now I just have to get onto version 6 to get the patch. :)

Max Slimmer's avatar
21
Max Slimmer
answered 2018-05-21 15:10:00 -0500
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments
0

I'm seeing this also.  I think we must be printing it again from the debugger code that handles this case, but I'm not sure yet.  We'll try to fix this soon.  Thanks for reporting this problem!

Wingware Support's avatar
3.9k
Wingware Support
answered 2018-05-21 09:07:00 -0500
edit flag offensive 0 remove flag delete link
more

Comments

We've issued a patch for Wing 6.0.12 that fixes this.  You can get it with Check for Updates from the Help menu.  The issue was that we were calling the sys.excepthook incorrectly during handling of logging.error.  This is relatively harmless with the default sys.excepthook but could be bad in code that sets a custom excepthook, so patching it seemed best.  Thanks again for reporting this!

Wingware Support's avatar Wingware Support (2018-05-21 13:24:00 -0500) edit
more
  • delete
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer