bpo-20104: Fix memory leaks and error handling in posix spawn#5418
Conversation
Sorry, something went wrong.
2512695 to
cb74d14
Compare
January 29, 2018 10:14
|
@vadmium There was a missing commit due to a failed push. I have amended the last commit to including all the fixes. In cb74d14 you will find the correct initial implementation. Sorry for the confusion. |
Sorry, something went wrong.
|
@vstinner Can you take a general look at this PR (if you have the time) to check that we are not missing something else? (The Docs are not included in this PR) |
Sorry, something went wrong.
gpshead
left a comment
There was a problem hiding this comment.
thanks for the cleanup!
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 And if you don't make the requested changes, you will be poked with soft cushions! |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @gpshead: please review the changes made to this pull request. |
Sorry, something went wrong.
https://bugs.python.org/issue20104