On Wed, Jul 26, 2000 at 10:11:40AM +0200, M . -A . Lemburg wrote: > Trent Mick wrote: > > > > On Linux32: > > - test_fork1 > > This fails/hangs/crashes inconsistently because (some little bird told me) > > the fork stuff and threads are incompatible. Am I right? Now that we are > > turning threads on by default what is the proper thing to do here? SHould > > test_fork1 be changed to skip if threads are enabled? > > Does this mean that a stock Python 1.6/2.0 interpreter will > not properly do fork() on Linux32 (even when using threads) ? > As I said: *some little bird told me*. (I think it was David.) I don't know, Marc-Andre. I am just waving a flag. Ignorantly yours, Trent -- Trent Mick TrentM@ActiveState.com
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