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 terry.reedy
Recipients asksol, brett.cannon, brian.curtin, jnoller, michael.foord, ncoghlan, pitrou, terry.reedy, vstinner
Date 2011-01-07.08:03:36
SpamBayes Score 1.2518848e-05
Marked as misclassified No
Message-id <>
On xp, changing from -m test to -m test.regrtest removed the extra craziness during and after the test run that I reported on pydev.

I think making at least a tempory fix to whatever -m test runs should be a release blocker so only individual tests and not the test process are broken. If necessary, just refuse to run under windows and say to use test.regrtest as before. (I believe I did use -m test.regrtest on 3.1 and 2.7 as -m test is not implemented for those.)
Date User Action Args
2011-01-07 08:03:40terry.reedysetrecipients: + terry.reedy, brett.cannon, ncoghlan, pitrou, vstinner, jnoller, michael.foord, brian.curtin, asksol
2011-01-07 08:03:40terry.reedysetmessageid: <>
2011-01-07 08:03:36terry.reedylinkissue10845 messages
2011-01-07 08:03:36terry.reedycreate