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 r.david.murray
Recipients brett.cannon, r.david.murray, sandro.tosi
Date 2011-01-21.20:20:16
SpamBayes Score 2.300428e-06
Marked as misclassified No
Message-id <1295641223.21.0.481577217315.issue10967@psf.upfronthosting.co.za>
In-reply-to
Content
I think we have already been moving in this director for quite some time.  Past policy is to only change things when we are working on that area of code anyway.  If someone wants to make some specific proposals to simplify regrtest by doing a wholesale move of test code away from a regrtest supported infrastructure to a unittest supported infrastructure, I think that's worth considering, but I think it should be done bit by bit with specific proposals to replace specific regrtest features.

Extending regrtest to support unittest test discovery directly is also a worthwhile specific proposal.

Do you intend this issue to be an "index issue" that links to issues with specific proposals?

(Note: see also the closely related issue 8273).
History
Date User Action Args
2011-01-21 20:21:50r.david.murrayunlinkissue10967 messages
2011-01-21 20:20:23r.david.murraysetrecipients: + r.david.murray, brett.cannon, sandro.tosi
2011-01-21 20:20:23r.david.murraysetmessageid: <1295641223.21.0.481577217315.issue10967@psf.upfronthosting.co.za>
2011-01-21 20:20:17r.david.murraylinkissue10967 messages
2011-01-21 20:20:16r.david.murraycreate