diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2019-11-19 20:11:20 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-19 20:11:20 (GMT) |
| commit | 829593a9262e67c72167c6cb20d383203b2ea410 (patch) | |
| tree | 9ea3f69d5837981978129ad4201752f7344b6117 /Python/future.c | |
| parent | 6c3b471c8c0bfd49c664d8ee7e95da3710fd6069 (diff) | |
| download | cpython-829593a9262e67c72167c6cb20d383203b2ea410.zip cpython-829593a9262e67c72167c6cb20d383203b2ea410.tar.gz cpython-829593a9262e67c72167c6cb20d383203b2ea410.tar.bz2 | |
bpo-38707: Fix for multiprocessing.Process MainThread.native_id (GH-17088)
This PR implements a fix for `multiprocessing.Process` objects; the error occurs when Processes are created using either `fork` or `forkserver` as the `start_method`.
In these instances, the `MainThread` of the newly created `Process` object retains all attributes from its parent's `MainThread` object, including the `native_id` attribute. The resulting behavior is such that the new process' `MainThread` captures an incorrect/outdated `native_id` (the parent's instead of its own).
This change forces the Process object to update its `native_id` attribute during the bootstrap process.
cc @vstinner
https://bugs.python.org/issue38707
Automerge-Triggered-By: @pitrou
(cherry picked from commit c6b20be85c0de6f2355c67ae6e7e578941275cc0)
Co-authored-by: Jake Tesler <jake.tesler@gmail.com>
Diffstat (limited to 'Python/future.c')
0 files changed, 0 insertions, 0 deletions