Hacker News Reader

> There is no sane way of forking a multithreaded program

The sane way of forking a multithreaded process is to exec immediately after.

It is possible to do more after a fork (cf. async-signal-safe), but it's hairy enough to just say — don't, always exec (similar to how doing actual work in a signal handler is generally a very bad idea).

If the child program is multithreaded then it's almost certainly not pure Python in the first place. So, wrap it up in `with nogil:` Cython statements and use the threading module (or concurrent.futures.ThreadPoolExecutor).

that is why 'forkserver' start method exists. https://docs.python.org/3/library/multiprocessing.html#conte...