➜

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 belopolsky
Recipients Alex.Roitman, belopolsky, brett.cannon, r.david.murray
Date 2010-08-12.03:03:43
SpamBayes Score 3.3938613e-07
Marked as misclassified No
Message-id <AANLkTik7y5rVnDkHpcF4x=g-98K01+qN0w5dwSVKhe7y@mail.gmail.com>
In-reply-to <1281581801.47.0.242942035934.issue9573@psf.upfronthosting.co.za>
Content 
On Wed, Aug 11, 2010 at 10:56 PM, Alex Roitman <report@bugs.python.org> wrote:
>
> Alex Roitman <rshura@gmail.com> added the comment:
>
> I can place it in a function.  But if I execute that function from anything other than main
> module, the fork() will be called while import lock is held, one way or another.  It will just
> happen in another module.  So what?

This discussion is now off-topic for the python bug tracker.  Please
ask questions on how to use python in an appropriate  forum such as
python-list.

The problem you have uncovered only occurs if fork() is called
*during* module import.  If you place fork() in a function, it will
not be called when you import the module or the function, - only when
you call the function.
History
Date User Action Args
2010-08-12 14:47:24belopolskyunlinkissue9573 messages
2010-08-12 03:03:47belopolskysetrecipients: + belopolsky, brett.cannon, r.david.murray, Alex.Roitman
2010-08-12 03:03:45belopolskylinkissue9573 messages
2010-08-12 03:03:43belopolskycreate