On Thu, Jan 6, 2011 at 4:00 PM, Terry Reedy <tjreedy at udel.edu> wrote:
>> Does it behave itself if you add "-x test_capi" to the command line?
>
> No, it gets worse. Really.
> Let me summarize a long post.
>
> Run 1: normal (as above)
> Process stops at capi test with Windows error message.
> Close command prompt window with [x] buttom (crtl-whatever had no effect).
>
> Run 2: normal (as before)
> Process reported capi test failure (supposedly fatal) but continued.
> Process just stopped ('hung') at concurrent futures. Close as before.
>
> 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
Does it all go back to normal if you use "python -m test.regrtest"
instead? Antoine discovered that multiprocessing on Windows gets
thoroughly confused if __file__ in the main module ends with
"__main__.py" (see http://bugs.python.org/issue10845)
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4