This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients loewis, neologix, vstinner
Date 2011-07-02.10:24:37
SpamBayes Score 2.225442e-12
Marked as misclassified No
Message-id <1309602278.01.0.220404635322.issue12469@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm also in favor of reverting this commit.

Hum, the problem is that the Python test suite creates a lot of threads. Revert the patch doesn't change anything for the test suite. I mean that all tests relying on signal delivery should (must) be running in a new fresh process, especially if the test expects that the signal is received immediatly (as described in POSIX). If we don't use a subprocess, the tests will fail sometimes if at least one thread was created before.

I will try to write a patch which implement all requirements we listed in this issue. I just fear that it is a little bit overkill just to support an "old" (?) OS. But fixing a test for FreeBSD 6 improves usually the reliability on other OSes, especially when we replaced fork() by subprocess.
History
Date User Action Args
2011-07-02 10:24:38vstinnersetrecipients: + vstinner, loewis, neologix
2011-07-02 10:24:38vstinnersetmessageid: <1309602278.01.0.220404635322.issue12469@psf.upfronthosting.co.za>
2011-07-02 10:24:37vstinnerlinkissue12469 messages
2011-07-02 10:24:37vstinnercreate