Message122416
| Author |
ezio.melotti |
| Recipients |
brett.cannon, eric.araujo, ezio.melotti, flox, gregory.p.smith, michael.foord, pitrou, r.david.murray, rhettinger |
| Date |
2010年11月25日.22:56:45 |
| SpamBayes Score |
2.6639603e-07 |
| Marked as misclassified |
No |
| Message-id |
<1290725806.72.0.224664589328.issue10273@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> * Moving the docs for type specific equality methods inside the docs for assertEqual to emphasize that those get dispatched automatically and need not be called directly.
I already fixed this on py3k, adding a section where the type-specific methods are described[0] and added a reference in the assertEqual description[1]. I also clarified that usually there's no need to call them directly even thought I don't see why they shouldn't do it if they want to use a specific test.
> * Changing assertRegexpMatches to assertRegex
And assertNotRegexpMatches -> assertNotRegex, assertRaisesRegexp -> assertRaisesRegex, assertWarnsRegexp -> assertWarnRegex?
Will the *Regexp forms be deprecated too?
[0]: http://docs.python.org/dev/py3k/library/unittest.html#type-specific-methods
[1]: http://docs.python.org/dev/py3k/library/unittest.html#unittest.TestCase.assertEqual |
|