8000 socket.IP{,V6}_RECVERR not exposed · Issue #118986 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

socket.IP{,V6}_RECVERR not exposed #118986

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.

Sign up for GitHub

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

Jump to bottom
Open
chrysn opened this issue May 13, 2024 · 1 comment
Open

socket.IP{,V6}_RECVERR not exposed #118986

chrysn opened this issue May 13, 2024 · 1 comment
Labels
type-feature A feature request or enhancement

Comments

@chrysn
Copy link
Contributor
chrysn commented May 13, 2024 •
edited by bedevere-app bot
Loading

Feature or enhancement

Proposal:

The IPV6_RECVERR socket option, which is needed to make good use of the MSG_ERRQUEUE recvmsg flag, is not exposed through socket, just through the private IN module.

sock.setsockopt(socket.IPPROTO_IPV6, socket.IPV6_RECVERR, 1)
data, ancdata, flags, addr = my_socket.recvmsg(2048, 1024, sock.MSG_ERRQUEUE)

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

People who want to use this only find some stackoverflow post that points them to the internal IN module, which thus makes its way into production code rather than just exposing two more socket option names.

Linked PRs
@chrysn chrysn added the type-feature A feature request or enhancement label May 13, 2024
@bedevere-app bedevere-app bot mentioned this issue May 13, 2024
Merged
chrysn added a commit to chrysn-pull-requests/cpython that referenced this issue Jun 24, 2024
@chrysn
pythongh-118986: expose socket.IPV6_RECVERR
a8f4628
@chrysn
Copy link
Contributor Author
chrysn commented Jun 24, 2024

Half of this got overtaken by the (more recent, but who is counting) #120056 by @sobolevn that introduced the IPv4 version but not the IPv6 version.

I have updated the news message to only claim what is now being added, but did not unify the NEWS fragment because those fragments are linked to PRs by their file names. It'd make sense to have a single entry in the change log – how should that be done?

Pinging @Eclips4 and @jeremyhylton as reviewers (Jeremy, thanks for insisting on alphabetical order, this made rebasing trivial).

chrysn added a commit to chrysn-pull-requests/cpython that referenced this issue Oct 17, 2024
@chrysn
pythongh-118986: expose socket.IPV6_RECVERR
9b88343
chrysn added a commit to chrysn-pull-requests/cpython that referenced this issue Oct 17, 2024
@chrysn
pythongh-118986: expose socket.IPV6_RECVERR
9e6384b
chrysn added a commit to chrysn-pull-requests/cpython that referenced this issue Oct 17, 2024
@chrysn
pythongh-118986: expose socket.IPV6_RECVERR
111a365
sobolevn pushed a commit that referenced this issue Oct 17, 2024
@chrysn
gh-118986: expose socket.IPV6_RECVERR (#118987)
b454662
ebonnal pushed a commit to ebonnal/cpython that referenced this issue Jan 12, 2025
@chrysn @ebonnal
pythongh-118986: expose socket.IPV6_RECVERR (python#118987)
f894b7f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type-feature A feature request or enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chrysn
0