I was composing a comment for a Python
try: …some code except (KeyboardInterrupt, EOFError): print("something") # Re-raise the exception for handling “X” in the stack. raise
… where “X” could be “lower” or “higher”, depending on your point of view, the system architecture, or the design intent of Python’s creators. So how are execution frames located in relation to each other in the stack, and in relation with the
__main__ module? Is there a best, most pythonic terminology?
__main__ scope is said to be where the “top-level” code executes, but this top-down concept isn't found anywhere else in the documentation. I searched for variations of the terms “Python stack direction” on search engines and found interesting but ultimately unsatisfying information.
Actually, the vocabulary used in the Python documentation is intuitive and implementation independent. Inner and outer are the words best used to describe the location of stack frames in relation to one another.
try: …some code except (KeyboardInterrupt, EOFError): print("something") # Re-raise the exception for handling outwards in the stack. raise
I found another reference that uses the top-down topology in the Python debugger module
pdb documentation. However, the technical writer must have found “up” and “down” to provide insufficient information so the concept of “newer” and “older” frame was appended in parenthesis.
Debugger Commands (extract)
- Move the current frame one level down in the stack trace (to a newer frame).
- Move the current frame one level up in the stack trace (to an older frame).
This reminds me of a familiar sentence! On an exit from an unhandled exception, the stack trace is printed and the first line is:
… and here again is the concept of newer and older frame.
Traceback (most recent call last):
In terms of topology, I guess this would translate as moving “towards the oldest/newest frame in the stack”.
Another thing: you raise — rather than drop — an exception, suggesting that older stacks frames are considered to be on top.
CommentsComment Atom Feed
There are no comments yet.