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 sbt
Recipients amaury.forgeotdarc, christian.heimes, jnoller, neologix, pitrou, python-dev, sbt, thebits, vstinner
Date 2012-05-18.16:02:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337356972.19.0.743223149906.issue12098@psf.upfronthosting.co.za>
In-reply-to
Content
> > Failure to build _multiprocessing will mean that multiprocessing cannot 
> > be imported.  So if the function goes somewhere in multiprocessing then 
> > it makes running the test suite with multiple processes dependent on the 
> > building of _multiprocessing.  Not sure if that is much of a problem
> > since one can just run the test suite normally.
> 
> I don't think that's a problem indeed.

Since multiprocessing also depends on threading, the change has broken the "AMD64 Fedora without threads 3.x" buildbot.  I had not realized that the buildbots ran the test suite using multiple processes.

I am not sure how best to refactor things -- I don't think multiprocessing should import test.support.  Maybe we should just live with the duplication.
History
Date User Action Args
2012-05-18 16:02:52sbtsetrecipients: + sbt, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, jnoller, neologix, python-dev, thebits
2012-05-18 16:02:52sbtsetmessageid: <1337356972.19.0.743223149906.issue12098@psf.upfronthosting.co.za>
2012-05-18 16:02:51sbtlinkissue12098 messages
2012-05-18 16:02:51sbtcreate