diff options
author | Gregory P. Smith <greg@krypto.org> | 2024-11-09 23:01:32 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-09 23:01:32 (GMT) |
commit | 9d08423b6e0fa89ce9cfea08e580ed72e5db8c70 (patch) | |
tree | 8015792119dca3a44c267e578d1799a12f654bad /Python/object_stack.c | |
parent | 266328552e922fd9030cd699e10a25f03a67c8ba (diff) | |
download | cpython-9d08423b6e0fa89ce9cfea08e580ed72e5db8c70.zip cpython-9d08423b6e0fa89ce9cfea08e580ed72e5db8c70.tar.gz cpython-9d08423b6e0fa89ce9cfea08e580ed72e5db8c70.tar.bz2 |
gh-117378: Fix multiprocessing forkserver preload sys.path inheritance. (GH-126538)
gh-117378: Fix multiprocessing forkserver preload sys.path inheritance.
`sys.path` was not properly being sent from the parent process when launching
the multiprocessing forkserver process to preload imports. This bug has been
there since the forkserver start method was introduced in Python 3.4. It was
always _supposed_ to inherit `sys.path` the same way the spawn method does.
Observable behavior change: A `''` value in `sys.path` will now be replaced in
the forkserver's `sys.path` with an absolute pathname
`os.path.abspath(os.getcwd())` saved at the time that `multiprocessing` was
imported in the parent process as it already was when using the spawn start
method. **This will only be observable during forkserver preload imports**.
The code invoked before calling things in another process already correctly sets `sys.path`.
Which is likely why this went unnoticed for so long as a mere performance issue in
some configurations.
A workaround for the bug on impacted Pythons is to set PYTHONPATH in the
environment before multiprocessing's forkserver process was started. Not perfect
as that is then inherited by other children, etc, but likely good enough for many
people's purposes.
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Diffstat (limited to 'Python/object_stack.c')
0 files changed, 0 insertions, 0 deletions