Unit testing multiprocessing code on Windows

[Matt Chaput]

Does anyone know the "right" way to write a unit test for code that uses 
multiprocessing on Windows?

The problem is that with both "python setup.py tests" and "nosetests", 
when they get to a multiprocessing test they spawn multiple copies of 
the testing suite. The test runner in PyDev works properly.

Maybe multiprocessing is starting new Windows processes by copying the 
command line of the current process, but if the command line is 
"nosetests", it's a one way ticket to an infinite explosion of processes.

Any thoughts?

Thanks,

Matt