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 eric.smith, flox, ncoghlan
Date 2010-03-17.14:15:16
SpamBayes Score 1.3253728e-06
Marked as misclassified No
Message-id <1268835319.11.0.265724278249.issue8155@psf.upfronthosting.co.za>
In-reply-to
Content
On a second look, there are a couple of things missing:
- the default value didn't actually get changed!
- we should add an explicit test that the no argument behaviour doesn't raise a warning by default

Since we don't really have an existing test suite for the support code, I'd suggest coopting test_sundry.py for the purpose.

I agree that an exception should be raised if the user passes in an expected warning but no warning at all is encountered.
History
Date User Action Args
2010-03-17 14:15:19ncoghlansetrecipients: + ncoghlan, eric.smith, flox
2010-03-17 14:15:19ncoghlansetmessageid: <1268835319.11.0.265724278249.issue8155@psf.upfronthosting.co.za>
2010-03-17 14:15:17ncoghlanlinkissue8155 messages
2010-03-17 14:15:16ncoghlancreate