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 michael.foord
Recipients BreamoreBoy, michael.foord, purcell, rbcollins
Date 2010-11-29.01:02:08
SpamBayes Score 3.847786e-08
Marked as misclassified No
Message-id <1290992529.86.0.569877175854.issue1705520@psf.upfronthosting.co.za>
In-reply-to
Content
__unittest needs to die (with appropriate deprecation).

I agree that a nicer API for marking functions and methods as needing to be excluded from unittest stacktraces would be useful. A decorator is a good way to expose that API to developers. Internally unittest could use the new API and __unittest can go away.

Introspecting stack frames is a bad way to implement this, as it doesn't play well with other implementations (like IronPython which doesn't have introspectable Python stack frames by default).
History
Date User Action Args
2010-11-29 01:02:10michael.foordsetrecipients: + michael.foord, purcell, rbcollins, BreamoreBoy
2010-11-29 01:02:09michael.foordsetmessageid: <1290992529.86.0.569877175854.issue1705520@psf.upfronthosting.co.za>
2010-11-29 01:02:08michael.foordlinkissue1705520 messages
2010-11-29 01:02:08michael.foordcreate