[Python-Dev] 3.2b2 fails test suite on (my) Windows XP

Dj Gilcrease digitalxero at gmail.com
Fri Jan 7 02:55:47 CET 2011

On Thu, Jan 6, 2011 at 1:00 AM, Terry Reedy <tjreedy at 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

More information about the Python-Dev mailing list