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 berker.peksag, ezio.melotti, jkloth, martin.panter, r.david.murray, serhiy.storchaka, vstinner
Date 2015-09-23.20:11:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This may be opening a can of worms, but I wonder if what we should really do is re-engineer regrtest from the ground up, keeping the existing regrtest around until we are satisfied with its replacement...and maybe some of the options wouldn't make the transition.  (I've used --single, but it's been a long time, and I think it may have only been when I was testing regrtest after modifying it...)

We could then shift buildbots over to the new command gradually (or, do a few first, and then all the rest).  Then when we're satisfied we could change -m test to use the new interface, but keep regrtest around, unmaintained, for a couple of releases for those who are still using it.

I haven't looked at Victor's code to see if I like his re-engineering, but I'm really talking about starting the re-engineering from the API, and only then thinking about the code to implement it.
Date User Action Args
2015-09-23 20:11:55r.david.murraysetrecipients: + r.david.murray, vstinner, jkloth, ezio.melotti, berker.peksag, martin.panter, serhiy.storchaka
2015-09-23 20:11:55r.david.murraysetmessageid: <>
2015-09-23 20:11:55r.david.murraylinkissue25220 messages
2015-09-23 20:11:55r.david.murraycreate