homepage

logging.error('...', exc_info=True) only displays the
frames downward. But I often need the upper frames, to debug a problem.
This example shows, that you don't see the "upper" frame in the stactrace. But that's information is important.
<pre>
import logging
def foo():
 try:
 raise Exception()
 except Exception, exc:
 logging.error('Exception occured: %s' % exc, exc_info=True)
def upper():
 foo()
upper()
</pre>
<pre>
===> python tmp/t.py
ERROR:root:Exception occured: 
Traceback (most recent call last):
 File "tmp/t.py", line 6, in foo
 raise Exception()
Exception
</pre>

Related: #1553375 

I tested it only on python 2.6. Can someone please look at more reset versions?

Until exc_info=True prints the current stack, I use this pattern:
import traceback
logging.error(u's...\nStack: %s' % (
 ''.join(traceback.format_stack())), exc_info=True)

This also happens on later versions. Since 2.x is essentially frozen, this feature request can't be implemented in 2.x, so recategorising as a Python 3.2 issue.
Here, a change in logging will either duplicate code in traceback.py or print the upper frames above the "Traceback (most recent call last):" line, which is not ideal.
The best way to implement in logging would be to wait for the implementation of the patch in #1553375, following which a change could be made in Formatter.formatException to invoke traceback.print_exception with the "fullstack" keyword parameter.

I'll close this, assuming that the stack_info keyword parameter added to logging calls in 3.2 will be sufficient.
I also removed the dependency on 1553375, which would prevent closure.