-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-123174: Add proto parameter to sock_connect #123175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Allow the selection of the protocol used by getaddrinfo by adding an additional, optional parameter proto_addr_info. If not specified, use the protocol used by the socket (= previous behaviour) This change is needed to allow custom protocols to be used with the sock_connect, because these protocols may raise an error when calling getaddrinfo (result in a "ai_proto not supported" error) An example of such protocol is MPTCP (https://mptcp.dev)
f3b91ee to
9e19f40
Compare
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
|
The following commit authors need to sign the Contributor License Agreement: |
Allow the selection of the protocol used by
getaddrinfoby adding an additional, optional parameterproto_addr_info.If not specified, use the protocol used by the socket (= previous behaviour).
This change is needed to allow custom protocols to be used with
sock_connect, because these protocols may raise an error when callinggetaddrinfo(result in aai_proto not supportederror).An example of such protocol is MPTCP (https://mptcp.dev)
proto_addr_infoargument to sock_connect in asyncio #123174