bpo-40060 Expose socket.TCP_NOTSENT_LOWAT on macOS in official builds#19402
bpo-40060 Expose socket.TCP_NOTSENT_LOWAT on macOS in official builds#19402dimaqq wants to merge 2 commits into
Conversation
|
I'm not sure why Azure Pipeline failed, and now it seems the build log was cleaned up and I can't see it. |
Sorry, something went wrong.
|
What now? |
Sorry, something went wrong.
|
The logs goes like: So, not my fault :) |
Sorry, something went wrong.
|
Re-running after Tests/Windows(x64) failed when test_subprocessing hung until timeout. All other tests in that run and all other runs passed. The same test passed on my machine on master and PR branch with re-compile. Re-running here from the error page failed after a minute. Going so far after 10 minutes after re-open. |
Sorry, something went wrong.
|
@terryjreedy feel free to use this PR to debug the build thing if you want :) |
Sorry, something went wrong.
Somehow, it turns out that
TCP_NOTSENT_LOWATthat's available since 3.7.x is not available in the official macOS builds 🙀This change exports the constant even if cpython is built against very old header files, as it's presumed to be the case for official macOS builds.
https://bugs.python.org/issue40060
https://bugs.python.org/issue40060