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, r.david.murray, rhettinger, sandro.tosi
Date 2012-09-19.22:31:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348093884.98.0.888176029872.issue10967@psf.upfronthosting.co.za>
In-reply-to
Content
One important piece is that regrtest currently has no tests (e.g. there is no test_regrtest.py), so changing it must be done more carefully.  How do people feel about new (or newly modified) regrtest classes and functions going into a different fully-tested module with its own test_* file.  Currently, regrtest is a mixture of definitions and "running code," so I would be leery of adding test_regrtest.

This could also be done by making regrtest a package, so that regrtest-related modules would be in a single directory.
History
Date User Action Args
2012-09-19 22:31:25chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, rhettinger, ezio.melotti, eric.araujo, r.david.murray, sandro.tosi
2012-09-19 22:31:24chris.jerdoneksetmessageid: <1348093884.98.0.888176029872.issue10967@psf.upfronthosting.co.za>
2012-09-19 22:31:24chris.jerdoneklinkissue10967 messages
2012-09-19 22:31:24chris.jerdonekcreate