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 Yaroslav.Halchenko, abingham, brian.curtin, eric.araujo, eric.snow, exarkun, fperez, michael.foord, nchauvat, ncoghlan, pitrou, r.david.murray
Date 2011-07-21.00:01:24
SpamBayes Score 0.019403243
Marked as misclassified No
Message-id <1311206485.56.0.665907577489.issue7897@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, and if we're not going to get clever with naming, how is the TestResult going to include the parameter repr in the failure report? That information will have to be stored on the TestCase. 

I would prefer this feature not to touch the TestResult - so any failure message cleverness should be done in the TestCase. It will be harder to maintain if this feature is spread out all the way through unittest.
History
Date User Action Args
2011-07-21 00:01:25michael.foordsetrecipients: + michael.foord, exarkun, ncoghlan, pitrou, eric.araujo, r.david.murray, brian.curtin, fperez, Yaroslav.Halchenko, nchauvat, abingham, eric.snow
2011-07-21 00:01:25michael.foordsetmessageid: <1311206485.56.0.665907577489.issue7897@psf.upfronthosting.co.za>
2011-07-21 00:01:25michael.foordlinkissue7897 messages
2011-07-21 00:01:24michael.foordcreate