Message179635
| Author |
chris.jerdonek |
| Recipients |
brett.cannon, chris.jerdonek, eric.araujo, ezio.melotti, python-dev, r.david.murray, serhiy.storchaka, terry.reedy, zach.ware |
| Date |
2013年01月11日.06:18:55 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1357885136.91.0.316419792507.issue16748@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
There are lots of modules to change here. I wonder if some or most of this couldn't be automated.
For example, is there any reason we couldn't write a script to check for the type of test duplication fixed documentation-wise in issue 16835? We could use such a script to find the classes that need to be updated when removing test_main (or to double-check existing test modules).
I don't know if there are ever times we want such duplication. |
|