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-14.19:45:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358192742.08.0.156316558614.issue16748@psf.upfronthosting.co.za>
In-reply-to
Content
> Also, I'm of the opinion that we'll end up with a higher quality result doing things by hand anyway.

Automation doesn't (and shouldn't) preclude careful review and modifications by hand.  My point was that it seems like it might be able to get you, say, 80% of the way there (e.g. by deleting test_main(), determining which classes are called by test_main(), adding ", unittest.TestCase", creating stub classes that could be retained or deleted).  Or at least provide some additional checks or info.  There are nearly 400 test files using test_main(), no?
History
Date User Action Args
2013-01-14 19:45:42chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, terry.reedy, ezio.melotti, eric.araujo, r.david.murray, python-dev, zach.ware, serhiy.storchaka
2013-01-14 19:45:42chris.jerdoneksetmessageid: <1358192742.08.0.156316558614.issue16748@psf.upfronthosting.co.za>
2013-01-14 19:45:42chris.jerdoneklinkissue16748 messages
2013-01-14 19:45:41chris.jerdonekcreate