Message 256920 - Python tracker

➜

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.

In-reply-to
Author	ronaldoussoren
Recipients	emptysquare, ionelmc, ronaldoussoren, serhiy.storchaka, vstinner, yselivanov
Date	2015年12月23日.15:47:29
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1450885649.36.0.0338975664572.issue25920@psf.upfronthosting.co.za>

Content
#25924 is related to this, I filed this after reading the blog post. The lock might not be necessary on OSX, and possibly on the other systems as well. Yury: resetting the lock in the child should be safe because after the fork the child only has a single thread that is returning from fork(2). The thread that acquired the lock does not exist in the child process.

Content

#25924 is related to this, I filed this after reading the blog post. The lock might not be necessary on OSX, and possibly on the other systems as well.
Yury: resetting the lock in the child should be safe because after the fork the child only has a single thread that is returning from fork(2). The thread that acquired the lock does not exist in the child process.

History
Date	User	Action	Args
2015年12月23日 15:47:29	ronaldoussoren	set	recipients: + ronaldoussoren, vstinner, ionelmc, serhiy.storchaka, yselivanov, emptysquare
2015年12月23日 15:47:29	ronaldoussoren	set	messageid: <1450885649.36.0.0338975664572.issue25920@psf.upfronthosting.co.za>
2015年12月23日 15:47:29	ronaldoussoren	link	issue25920 messages
2015年12月23日 15:47:29	ronaldoussoren	create

homepage