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 ncoghlan
Recipients asksol, brett.cannon, brian.curtin, georg.brandl, jnoller, michael.foord, ncoghlan, pitrou, terry.reedy, vstinner
Date 2011-01-28.15:09:17
SpamBayes Score 0.00048491522
Marked as misclassified No
Message-id <>
There isn't really much "-m test" can do to flag this - multiprocessing is making assumptions about the meaning of __file__ that may be flat out invalid when -m is used to execute the main module.

Fixing that properly is going to require a PEP so the interpreter preserves the information that multiprocessing needs in order to spawn the child process correctly on Windows. (I already have that on my personal todo list for 3.3)

I'm not sure what to do for 3.2. We could comment out the assert, since that will be slightly less broken than the current total failure (it will still be slightly broken, though).
Date User Action Args
2011-01-28 15:09:17ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, terry.reedy, pitrou, vstinner, jnoller, michael.foord, brian.curtin, asksol
2011-01-28 15:09:17ncoghlansetmessageid: <>
2011-01-28 15:09:17ncoghlanlinkissue10845 messages
2011-01-28 15:09:17ncoghlancreate