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 ncoghlan
Recipients ncoghlan, pitrou, vstinner
Date 2012-04-25.05:49:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335332949.45.0.352234246799.issue14665@psf.upfronthosting.co.za>
In-reply-to
Content
Victor's argument makes sense to me. What I'd be inclined to do is shout at the reader a bit in the traceback header by making it:

    Traceback (most recent call FIRST):

And put a comment in the source code with the gist of what Victor wrote above (i.e. internal state may be corrupted, we do the best we can with what we've got, and that means printing the traceback from the inside out)
History
Date User Action Args
2012-04-25 05:49:09ncoghlansetrecipients: + ncoghlan, pitrou, vstinner
2012-04-25 05:49:09ncoghlansetmessageid: <1335332949.45.0.352234246799.issue14665@psf.upfronthosting.co.za>
2012-04-25 05:49:08ncoghlanlinkissue14665 messages
2012-04-25 05:49:08ncoghlancreate