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 Arfrever, amaury.forgeotdarc, brett.cannon, chris.jerdonek, eric.snow, georg.brandl, meador.inge, ncoghlan, pitrou
Date 2012-07-30.11:23:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343647422.01.0.271559466884.issue15486@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the actual code - I don't think it actually makes sense to strip the frames in this case. Unlike the previous examples, it only comes up if someone is doing something deliberately pathological, at which point a little noise in the traceback is the least of your worries.

Updated patch just drops that test case entirely and only has the changes that simplify the frame removal code. Since Georg isn't on IRC right now, assigning him to decide if he wants this version in beta 2 rather than the current "multiple exit points" approach.
History
Date User Action Args
2012-07-30 11:23:42ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, amaury.forgeotdarc, pitrou, Arfrever, meador.inge, chris.jerdonek, eric.snow
2012-07-30 11:23:42ncoghlansetmessageid: <1343647422.01.0.271559466884.issue15486@psf.upfronthosting.co.za>
2012-07-30 11:23:41ncoghlanlinkissue15486 messages
2012-07-30 11:23:41ncoghlancreate