On zondag, jun 29, 2003, at 23:12 Europe/Amsterdam, L.C. (Laurentiu C. Badea) wrote: > The simple program below launches a thread, then fork()s and attempts > to clean > the mess up on exit like the nice process it is. Only problem is, the > child does > not want to die, looks like it detached and is sitting on > schedule_timeout() > (according to ps). I haven't looked at it in detail, but this could well be a problem. And if it is then it may need a different solution as your suggestion (clean up the mess in os.fork()), as fork() could conceivably be called from extension modules. Hmm, no, these should be good citizens and call PyOS_AfterFork(), I guess. Anyway: you should submit a bug report for this so it doesn't get lost. -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
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