-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Consistently goto exit in py_posix_spawn
#142532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
You need to update the branch to fix CI. |
|
Thanks @johnslavik for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
|
Thanks @johnslavik for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Consistently use `goto exit;` in `py_posix_spawn()`. (cherry picked from commit 8cfa351) Co-authored-by: Bartosz Sławecki <[email protected]>
Consistently use `goto exit;` in `py_posix_spawn()`. (cherry picked from commit 8cfa351) Co-authored-by: Bartosz Sławecki <[email protected]>
|
GH-142581 is a backport of this pull request to the 3.13 branch. |
|
GH-142582 is a backport of this pull request to the 3.14 branch. |
|
Merged, thanks for the fix! |
Fix os.posix_spawn() error handling (GH-142532) Consistently use `goto exit;` in `py_posix_spawn()`. (cherry picked from commit 8cfa351) Co-authored-by: Bartosz Sławecki <[email protected]>
Consistently use `goto exit;` in `py_posix_spawn()`.
return NULLhas quite the same effect right now --exitdoesn't have anything to clean up at this point of execution.Nevertheless, I think it's better to reduce the possibility of something slipping through in the future.
Especially since all the surrounding preconditions do use
goto exit.CC @ZeroIntensity
extension-modules,skip issue,skip news