Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-May/065054.html below:

[Python-Dev] pthreads, fork, import, and execvp

• Previous message: [Python-Dev] pthreads, fork, import, and execvp
• Next message: [Python-Dev] pthreads, fork, import, and execvp
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ronald Oussoren wrote:
> Wouldn't this specific problem be fixed if os.fork were to acquire the
> import lock before calling fork(2)?

Right. Of course, you need to release the lock then both in the parent
and the child. Also, all places that currently do PyOs_AfterFork should
get modified (i.e. fork1, and forkpty also).

Regards,
Martin

• Previous message: [Python-Dev] pthreads, fork, import, and execvp
• Next message: [Python-Dev] pthreads, fork, import, and execvp
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4