Unit testing multiprocessing code on Windows

David 71david at libero.it
Sat Feb 19 07:19:57 CET 2011


Il Thu, 17 Feb 2011 18:31:59 -0500, Matt Chaput ha scritto:

> 
> The problem is that with both "python setup.py tests" and "nosetests", 

> 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.

You can adapt this code to inhibit test execution if another process is
testing yet.
http://code.activestate.com/recipes/474070-creating-a-single-instance-application/




More information about the Python-list mailing list