Message 113656 - 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.

Author	Alex.Roitman
Recipients	Alex.Roitman, belopolsky, brett.cannon, r.david.murray
Date	2010-08-12.05:21:49
SpamBayes Score	0.00019374267
Marked as misclassified	No
Message-id	<1281590512.63.0.818565918467.issue9573@psf.upfronthosting.co.za>
In-reply-to

Content
1. If fork should not be called during import, it could raise an exception when invoked from import. But it does not. Is that a bug then? BTW, fork during import worked with python 2.4 just fine. 2. The whole issue7242 was devoted to work out import locks during forking. 5 months ago r78527 was committed to to just that (although it is not perfect). If this is not the proper use case then had it been done in error? 3. belopolsky: Thanks for the advice to use the mailing list. I'd appreciate it if instead you refrained from publishing my email address on this page.

1. If fork should not be called during import, it could raise an exception when invoked from import.  But it does not.  Is that a bug then?  BTW, fork during import worked with python 2.4 just fine.

2. The whole issue7242 was devoted to work out import locks during forking. 5 months ago r78527 was committed to to just that (although it is not perfect). If this is not the proper use case then had it been done in error?

3. belopolsky: Thanks for the advice to use the mailing list.  I'd appreciate it if instead you refrained from publishing my email address on this page.

History
Date	User	Action	Args
2010-08-12 05:21:53	Alex.Roitman	set	recipients: + Alex.Roitman, brett.cannon, belopolsky, r.david.murray
2010-08-12 05:21:52	Alex.Roitman	set	messageid: <1281590512.63.0.818565918467.issue9573@psf.upfronthosting.co.za>
2010-08-12 05:21:51	Alex.Roitman	link	issue9573 messages
2010-08-12 05:21:49	Alex.Roitman	create