➜

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 vandyswa
Recipients vandyswa
Date 2010-06-23.19:21:25
SpamBayes Score 0.22566128
Marked as misclassified No
Message-id <1277320886.89.0.906554449905.issue9064@psf.upfronthosting.co.za>
In-reply-to
Content 
In very deep stack traces (like runaway recursion) it can be a pain to get up to the top of the stack to see what kicked it off.  I've enhanced up/down to take a numeric argument for the number of positions to traverse, or -1 to go to the top/bottom.  Sample patch included.
History
Date User Action Args
2010-06-23 19:21:27vandyswasetrecipients: + vandyswa
2010-06-23 19:21:26vandyswasetmessageid: <1277320886.89.0.906554449905.issue9064@psf.upfronthosting.co.za>
2010-06-23 19:21:25vandyswalinkissue9064 messages
2010-06-23 19:21:25vandyswacreate