Unit testing multiprocessing code on Windows

M

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 testing any code that starts Processes they spawn
multiple copies of the testing suite (i.e. the new processes start
running tests as if they were started with "python setup.py
tests"/"nosetests"). 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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,483
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top