This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nirai
Recipients Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner
Date 2011-06-30.14:16:32
SpamBayes Score 0.005795378
Marked as misclassified No
Message-id <1309443393.6.0.626834234358.issue6721@psf.upfronthosting.co.za>
In-reply-to
Content
Well, I ping my view that we should:

1) Add general atfork() mechanism.
2) Dive into the std lib and add handlers one by one, that depending on case, either do the lock/init thing or just init the state of the library to some valid state in the child.

Once this mechanism is in place and committed with a few obvious handlers such as the one for the logging library, other handlers can be added over time.

Following this path we will slowly resolve the problem, handler by handler, without introducing the invalid state problem.
History
Date User Action Args
2011-06-30 14:16:33niraisetrecipients: + nirai, gregory.p.smith, pitrou, vstinner, bobbyi, neologix, Giovanni.Bajo, sdaoden, avian
2011-06-30 14:16:33niraisetmessageid: <1309443393.6.0.626834234358.issue6721@psf.upfronthosting.co.za>
2011-06-30 14:16:33nirailinkissue6721 messages
2011-06-30 14:16:32niraicreate