[Python-checkins] r86467 - in python/branches/py3k: Doc/library/logging.rst Lib/logging/__init__.py Misc/NEWS

Nick Coghlan ncoghlan at gmail.com
Mon Nov 15 14:24:01 CET 2010

On Mon, Nov 15, 2010 at 7:33 AM, vinay.sajip <python-checkins at python.org> wrote:
> +   .. attribute:: stack_info
> +
> +      Stack frame information (where available) from the bottom of the stack
> +      in the current thread, up to and including the stack frame of the
> +      logging call which resulted in the creation of this record.
> +

Interesting - my mental model of the call stack is that the outermost
frame is the top of the stack and the stack grows downwards as calls
are executed (there are a few idioms like "recursive descent", the
intuitive parallel with "inner functions" being lower in the stack
than "outer functions" as well as the order in which Python prints
stack traces that reinforce this view).

According to the sys.getframe documentation, my mental model is wrong though :)

(I'll note that the documentation of frame objects in the language
reference itself appears a little confused on the matter - either that
or I'm completely misunderstanding when writing to f_lineno will work)


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-checkins mailing list