This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Andrew.Harrington
Recipients Andrew.Harrington, kbk, roger.serwy, terry.reedy
Date 2015-02-28.01:39:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
I was using this without looking at documentation, as a newbies would.
Graying and disabling until after an exception makes sense, but even the
menu item name is misleading:  any time the program is running there is a
stack that you might want to view.   Better labels in the menu than "Stack
Viewer"  would be "stack trace" or "stack after exception" (maybe too long)
or "stack after crash".

On Fri, Feb 27, 2015 at 4:49 PM, Terry J. Reedy <>

> Terry J. Reedy added the comment:
> Verified on Windows whenever the debugger is active, meaning that a
> program is running.  (Debug On just means that it will become active when
> code is run.) No stepping is needed; debugger can be pointing to the inital
> docstring line.  For me also, Idle stops and has to be externally closed,
> as opposed to totally disappearing by itself.
> The doc for Stack Viewer says "Show the stack traceback of the last
> exception".   Example:
> >>> 1/0
> Traceback (most recent call last):
>   File "<pyshell#0>", line 1, in <module>
>     1/0
> ZeroDivisionError: division by zero
> >>>
> Selecting Stack Viewer pops up a viewer box.  This still works after
> >>>
> turns the debugger on but inactive.  Entering anything at the prompt
> disables viewing the 'last' exception, contrary to my understanding of the
> short doc.  So I might add '(if no other code has been run)' to the doc.
> Selecting Stack Viewer while a program is running (sleeping in this next
> example)
> >>> import time; time.sleep(10); 1/0
> brings up a box after the exception is printed.  So 'last exception' can
> actually be 'next exception'.  But in this case, the user process is left
> 'running' and no '>>> ' prompt appears, and one must Shell -> Restart to do
> anything further.  This is not good behavior.
> When one selects Debug -> Debugger while user code is running, Idle brings
> up a message box "Don't debug now: You can only toggle the debugger when
> idle".  I think Debug -> Stack Viewer should be similarly disabled, though
> perhaps graying out the menu entry might be better. It could also be grayed
> out when there the 'last exception' cannot be viewed because other code has
> been run.  Stack Viewer should definitely be ignored when the debugger is
> active, and I see no need to let people select it *before* an exception
> occurs and the prompt is displayed.  The next menu entry, Auto-open Stack
> Viewer, takes care of opening upon future exceptions.
> ----------
> stage:  -> needs patch
> title: IDLE hangs with debug on and stack viewer -> IDLE hangs when
> selecting Stack View with debug active
> _______________________________________
> Python tracker <>
> <>
> _______________________________________

Dr. Andrew N. Harrington
  Computer Science Department
  Graduate Program Director
  Loyola University Chicago
  529 Lewis Tower, 111 E. Pearson St. (Downtown)
  104 Loyola Hall, 1032 W. Sheridan Road (Rogers Park)
Phone: 312-915-7982
Fax:    312-915-7998 (as professor, not gpd role)
Date User Action Args
2015-02-28 01:39:21Andrew.Harringtonsetrecipients: + Andrew.Harrington, terry.reedy, kbk, roger.serwy
2015-02-28 01:39:20Andrew.Harringtonlinkissue23544 messages
2015-02-28 01:39:18Andrew.Harringtoncreate