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 r.david.murray
Recipients Red HamsterX, ajaksu2, amaury.forgeotdarc, r.david.murray, sanxiyn
Date 2009-07-29.16:40:20
SpamBayes Score 2.7445683e-06
Marked as misclassified No
Message-id <1248885622.32.0.573001583875.issue1466065@psf.upfronthosting.co.za>
In-reply-to
Content
If "it may be noisy where it was silent before", then add one of those
cases and make sure the noise doesn't happen before your fix, and does
happen after.

If you have to check the value of the exception string for other tests,
then do so.  There are plenty of examples of this in the existing tests,
(see the pydoc tests, for example).  If you can limit what you test for
so that the test will be resitent to changes in the exact text, so much
the better.  You can use  assertRaisesRegexp for this in 2.7.
History
Date User Action Args
2009-07-29 16:40:22r.david.murraysetrecipients: + r.david.murray, amaury.forgeotdarc, sanxiyn, ajaksu2, Red HamsterX
2009-07-29 16:40:22r.david.murraysetmessageid: <1248885622.32.0.573001583875.issue1466065@psf.upfronthosting.co.za>
2009-07-29 16:40:21r.david.murraylinkissue1466065 messages
2009-07-29 16:40:20r.david.murraycreate