> Although I would be in favor of an atfork callback registration system > (similar to atexit), it seems there is no way to solve the fork() > problem automatically with this. Any attempt to acquire/release locks > automatically will lead to deadlocks, as it is necessary to know the > exact program workflow to take locks in the right order.
That's not true. If the creator of the locks would register an atfork callback set, they could arrange it to acquire the locks in the right order (in cases where the order matters). Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
