On Mon, Nov 15, 2010 at 7:33 AM, vinay.sajip <python-check...@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) Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
