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 vinay.sajip
Recipients ggenellina, guettli, hoffman, ncoghlan, news1234, pakal, r.david.murray, vinay.sajip, ysj.ray
Date 2010-11-14.21:38:17
SpamBayes Score 6.82571e-11
Marked as misclassified No
Message-id <1289770698.96.0.197646876863.issue1553375@psf.upfronthosting.co.za>
In-reply-to
Content
I've implemented an optional keyword argument stack_info (defaulting to False) for all logging calls. If specified as True, a line 

Stack (most recent call last):

is printed, followed by the output of traceback.print_stack(). This is output after any exception information.

Checked into py3k (r86467), please can interested parties check if it meets the logging use case mentioned when the ticket was created?

Regression tests pass OK, and docs updated in this checkin.
History
Date User Action Args
2010-11-14 21:38:19vinay.sajipsetrecipients: + vinay.sajip, guettli, hoffman, ncoghlan, ggenellina, pakal, r.david.murray, news1234, ysj.ray
2010-11-14 21:38:18vinay.sajipsetmessageid: <1289770698.96.0.197646876863.issue1553375@psf.upfronthosting.co.za>
2010-11-14 21:38:17vinay.sajiplinkissue1553375 messages
2010-11-14 21:38:17vinay.sajipcreate