-
-
Notifications
You must be signed in to change notification settings - Fork 33.3k
bpo-41108: add IP_PORTRANGE* constants to the socket module
#21127
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
Open
ngie-eign
wants to merge
3
commits into
python:main
Choose a base branch
from
ngie-eign:add-more-ip_range-constants-to-socket
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
bpo-41108: add IP_PORTRANGE* constants to the socket module
#21127
ngie-eign
wants to merge
3
commits into
python:main
from
ngie-eign:add-more-ip_range-constants-to-socket
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
IP_PORTRANGE* constants to the socket moduleIP_PORTRANGE* constants to the socket module
299a942 to
f73ff38
Compare
ZackerySpytz
reviewed
Aug 5, 2020
Misc/NEWS.d/next/Core and Builtins/2020-06-24-21-09-04.bpo-41108.wIy4D8.rst
Outdated
Show resolved
Hide resolved
f73ff38 to
fe85b3e
Compare
ngie-eign
commented
Oct 19, 2025
afe7912 to
04831c8
Compare
a202a0a to
71b4b4d
Compare
71b4b4d to
c128717
Compare
|
@ZackerySpytz : fixed the issues with the news blurb. Do you have an opportunity to review this, or is someone else on the dev team available? |
`IP_PORTRANGE*` can be used for getting/setting port ranges on a per socket basis, as opposed to a system wide basis, in conjunction with calls like `socket.getsockopt` and `socket.setsockopt`. This functionality is available on \*BSD and Linux. Signed-off-by: Enji Cooper <[email protected]>
c128717 to
908a86e
Compare
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.
IP_PORTRANGE*can be used for getting/setting port ranges on a persocket basis, as opposed to a system wide basis, in conjunction with calls
like
socket.getsockoptandsocket.setsockopt.This functionality is available on *BSD and Linux.
Signed-off-by: Enji Cooper [email protected]
Closes: #85280