implemented debug() editor function which lets you navigate in the stack frame #192
Conversation
|
|
||
| return excepthook | ||
|
|
||
|
|
||
| def run_editor_on_exception(root_path=None, usercode_traceback=True): | ||
| def run_editor_on_exception(root_path=None, usercode_traceback=True, usercode_frame=True): |
There was a problem hiding this comment.
Don't forget to repeat the new argument in the file viewer/__init__.pt in the larray repository
| sys.excepthook = orig_except_hook | ||
|
|
||
|
|
||
| def debug(depth=0): |
There was a problem hiding this comment.
add this function to the larray repository ?
|
|
…ack frame run_editor_on_exception now uses debug so that we can navigate the traceback
Doesn't seem better. The "usercode" part of the names is fine IMO, but the "traceback" and "frame" parts are probably chinese to most of our users... even though this is not a big deal since they are not the target for such arguments. I expect we (or I?) will be the only one(s) using those arguments, but to me at least, they are very useful. I only want our typical users to understand the arguments enough to know they should probably not touch them 😉, and developers like you to understand them enough to actually use them. |
|
In that case, merge the PR as it. |
run_editor_on_exception now uses debug so that we can navigate the traceback
PS: I am not really happy with the names usercode_traceback (which already existed) and usercode_frame (new).
I just couldn't find anything better. Do you have a suggestion?