Message175980
2012/11/20 Christian Heimes <report@bugs.python.org>
> IFF we are going to walk the hard and rocky road of exception handling,
> then we are going to need at least four hooks and a register function that
> takres four callables as arguments: register(prepare, error, parent,
> child). Each prepare() call pushes an error handling onto a stack. In case
> of an exception in a prepare handler, the error stack is popped until all
> error handlers are called. This approach allows a prepare handler to
> actually prevent a fork() call from succeeding.
>
FWIW, PyPy already has a notion of fork hooks:
https://bitbucket.org/pypy/pypy/src/b4e4017909bac6c102fbc883ac8d2e42fa41553b/pypy/module/posix/interp_posix.py?at=default#cl-682
Various subsystems (threads cleanup, import lock, threading.local...)
register their hook functions.
You may want to experiment from there :-)
A new "atfork" module would be easy to implement. |
|
Date |
User |
Action |
Args |
2012-11-20 09:11:52 | Amaury.Forgeot.d'Arc | set | recipients:
+ Amaury.Forgeot.d'Arc, twouters, gregory.p.smith, christian.heimes, sbt |
2012-11-20 09:11:52 | Amaury.Forgeot.d'Arc | link | issue16500 messages |
2012-11-20 09:11:51 | Amaury.Forgeot.d'Arc | create | |
|