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 mattchaput
Recipients amaury.forgeotdarc, mattchaput
Date 2011-02-18.16:49:29
SpamBayes Score 3.218198e-11
Marked as misclassified No
Message-id <1298047771.27.0.397318087415.issue11240@psf.upfronthosting.co.za>
In-reply-to
Content
I don't know what to tell you... to the best of my knowledge there's absolutely no way for my code to kick off the entire test suite -- I always do that through PyDev (which doesn't cause the bug, by the way). The closest thing is the boilerplate at the bottom of every test file:

if __name__ == "__main__":
    unittest.main()

...but even that would only start the tests in that file, not the entire suite.

Another thing that makes me think multiprocessing is re-running the original command line is that if I use "python setup.py test" to start the tests, when it gets to the MP tests it seems to run that command for each Process that gets started, but if I use "nosetests", it seems to run "nosetests" for each started Process.
History
Date User Action Args
2011-02-18 16:49:31mattchaputsetrecipients: + mattchaput, amaury.forgeotdarc
2011-02-18 16:49:31mattchaputsetmessageid: <1298047771.27.0.397318087415.issue11240@psf.upfronthosting.co.za>
2011-02-18 16:49:30mattchaputlinkissue11240 messages
2011-02-18 16:49:29mattchaputcreate