On Thu, Jan 6, 2011 at 1:00 AM, Terry Reedy <tjre...@udel.edu> wrote: > On 1/5/2011 8:59 PM, Nick Coghlan wrote: > Run 3: -x test_capi test_concurrent_futures > Instead of the normal output I expected, I got some of the craziest stuff I > have ever seen. Things like > " > assert main_name not in sys.modules, main_name > AssertionError: __main__ > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "C:\Programs\Python32\lib\multiprocessing\forking.py", line 369, in > main > prepare(preparation_data) > File "C:\Programs\Python32\lib\multiprocessing\forking.py", line 477, > " > were printed 100s of times intermixed with the normal sequential test > startup lines. They stopped after text_sax started and output became normal > through the end of the report.
The 100's or 1000's of processes popping up is cause by a test that uses multi-processing and failing to have the if __name__ == '__main__' check around where it creates the processes _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
