bpo-35537: Change subprocess to use posix_spawnp instead of posix_spawn#11917
bpo-35537: Change subprocess to use posix_spawnp instead of posix_spawn#11917nanjekyejoannah wants to merge 6 commits into
Conversation
vstinner
left a comment
There was a problem hiding this comment.
Ah, one last thing: your PR makes the following doc outdated:
https://docs.python.org/dev/whatsnew/3.8.html#optimizations
Please update: "The subprocess module can now use the os.posix_spawn() function...": it's now posix_spawnp. Moreover, "the executable path contains a directory." condition can now be removed. Well, update the doc :-)
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
The previous attempt was reverted because of semantic differences between |
Sorry, something went wrong.
68d7580 to
6309240
Compare
February 18, 2019 13:43
Oh.... It was last month but I already completely forgot my own previous attempt :-( |
Sorry, something went wrong.
|
@nanjekyejoannah: Sorry, but I forgot that I made exactly the same change last month but we had to revert it... See @izbyshev's comment: I close your PR. |
Sorry, something went wrong.
|
cool noted!! |
Sorry, something went wrong.
I have added a change to make subprocess.py to use posix_spawnp instead of posix_spawn.
cc @vstinner
https://bugs.python.org/issue35537