bpo-20104: Remove posix_spawn from 3.7#6794
Conversation
3284174 to
c200683
Compare
May 14, 2018 15:10
c200683 to
a65ef05
Compare
May 14, 2018 16:01
gpshead
left a comment
There was a problem hiding this comment.
this looks straight forward.
I suggest dropping the changes to aclocal.m4, configure.ac, configure, pyconfig.h.in that remove the check for the API. It is fine for us to leave the autoconf script in 3.7 testing for the posix_spawn function.
Sorry, something went wrong.
|
@ned-deily - what would you like to see for a Misc/NEWS.d entry for this. os.posix_spawn appeared in some betas but we're removing it before rc1. document it as being removed again? or just remove all prior mentions of adding it? |
Sorry, something went wrong.
and reference the removal from the old news entry where it was added.
We can keep the configure test for posix_spawn, we'll need it in the future and having it in pyconfig.h will be convenient in case any 3.7 extension module wants to use it.
|
okay, i've undone the configure changes and done the news entries. just waiting for the various CI runs to complete (overloaded by the sprints) before merging. |
Sorry, something went wrong.
https://bugs.python.org/issue20104