bpo-31878: Fix _socket module compilation on Cygwin#4137
Conversation
|
I think it is better to remove PYCC_VACPP in a separate commit. |
Sorry, something went wrong.
I agree, it's distributing to have both changes in the same PR. Moreover, for the Cygwin PR, please explain your change in the commit message. Explain that your change adds the ioctl.h include on Cygwin. |
Sorry, something went wrong.
|
It is in a separate commit, but the same PR. I will make a separate PR--it just seemed like very minor code cleanup. |
Sorry, something went wrong.
|
Rebased: Dropped the |
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
Thanks! |
Sorry, something went wrong.
|
Thanks @embray for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Sorry, something went wrong.
(cherry picked from commit 63ae044)
Wait. For me, Cygwin means supporting a new platform. It was never supported officially. I'm against backporting such change. |
Sorry, something went wrong.
|
"It is in a separate commit, but the same PR. I will make a separate PR--it just seemed like very minor code cleanup." Please CC-me for your new "cleanup" PR, I like it ;-) |
Sorry, something went wrong.
|
Thanks @embray for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 2.7. |
Sorry, something went wrong.
|
Sorry, @embray and @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
In Cygwin, as on OSX,
ioctl()is declared insys/ioctl.h, and so needs this include. This is necessary for the_socketmodule to compile successfully on that platform.https://bugs.python.org/issue31878