bpo-37370: AF_UNIX should be supported on Windows #14302
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
test_socketserver just failed on my dev machine. |
|
This PR is not ready yet. There are a bunch of tests failing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AF_UNIX has been supported on windows since version 1803 (build 17134)
see https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
Enabling support for AF_UNIX will enable better peer-to-peer connectivity scenarios for Azure IoT Edge. The changes to enable AF_UNIX on Windows seem small and low risk.
I need feedback on these proposed changes
@zooba
https://bugs.python.org/issue37370