[PR #10962/84decfe5 backport][3.12] add example of setting network interface in custom socket creation #10966
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.
This is a backport of PR #10962 as merged into master (84decfe).
What do these changes do?
Some users may want to specific network interface used by client session (as in #6383 and #7132 ). In aiohttp 3.12, this can be done more gracefully with
socket_factory
inTCPConnector
. I think it would be helpful to mention it insocket_factory
's documentation as one of its common usecases.Are there changes in behavior for the user?
Is it a substantial burden for the maintainers to support this?
Related issue number
closes #7132
Checklist
CONTRIBUTORS.txt
CHANGES/
folder