Author chris.jerdonek
Recipients a.kasyanov, asvetlov, chris.jerdonek, ezio.melotti, georg.brandl, orsenthil, r.david.murray, tshepang
Date 2012-12-24.16:33:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1356366822.64.0.98084574927.issue15302@psf.upfronthosting.co.za>
In-reply-to
Content
> why regrlib.py at all?  Why isn't the code in regrtest.py?

It was for a few related reasons.  It was primarily to make it easier to reason about testing regrtest, and to avoid at the outset any pitfalls that might arise from the circularity of regrtest testing itself.  For example, the regrtest module seems to carry a fair bit of state and top-level code, whereas the "library" module being added would be stateless.  It would also let us maintain an obvious line between what is tested and what is not.

There was no discussion of creating a package.  However, if we go this route I would foresee moving functionality from regrtest to the library module as we expand the amount of regrtest-support code under test.
History
Date User Action Args
2012-12-24 16:33:42chris.jerdoneksetrecipients: + chris.jerdonek, georg.brandl, orsenthil, ezio.melotti, r.david.murray, asvetlov, tshepang, a.kasyanov
2012-12-24 16:33:42chris.jerdoneksetmessageid: <1356366822.64.0.98084574927.issue15302@psf.upfronthosting.co.za>
2012-12-24 16:33:42chris.jerdoneklinkissue15302 messages
2012-12-24 16:33:42chris.jerdonekcreate