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 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.
History
Date User Action Args
2013-01-11 06:18:57chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, terry.reedy, ezio.melotti, eric.araujo, r.david.murray, python-dev, zach.ware, serhiy.storchaka
2013-01-11 06:18:56chris.jerdoneksetmessageid: <1357885136.91.0.316419792507.issue16748@psf.upfronthosting.co.za>
2013-01-11 06:18:56chris.jerdoneklinkissue16748 messages
2013-01-11 06:18:55chris.jerdonekcreate