IN module removed in python 3.x; socket doesn't fill in the gap with IP_PORTRANGE*

[ngie-eign]

BPO	41108
Nosy	@ngie-eign
PRs	gh-85280: add IP_PORTRANGE* constants to the socket module #21127

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2020-06-24.21:08:47.876>
labels = ['3.7', '3.8', '3.9', '3.10', 'extension-modules', 'type-feature']
title = "IN module removed in python 3.x; socket doesn't fill in the gap with IP_PORTRANGE*"
updated_at = <Date 2020-06-24.21:08:47.876>
user = 'https://github.com/ngie-eign'

bugs.python.org fields:

activity = <Date 2020-06-24.21:08:47.876>
actor = 'ngie'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2020-06-24.21:08:47.876>
creator = 'ngie'
dependencies = []
files = []
hgrepos = []
issue_num = 41108
keywords = []
message_count = 1.0
messages = ['372282']
nosy_count = 1.0
nosy_names = ['ngie']
pr_nums = ['21127']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41108'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']

[ngie-eign]

The group that I work with uses the IN.py module to access constants available in netinet/in.h on BSD when adjusting socket port ranges.

This compile-time module was never ported forward to 3.x and equivalent functionality doesn't exist in the socket module. This bug will address that issue.