Repository navigation
socket.IP{,V6}_RECVERR not exposed #118986
Description
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.
Activity
pythongh-118986: expose socket.IPV6_RECVERR
chrysn commentedon 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).
pythongh-118986: expose socket.IPV6_RECVERR
pythongh-118986: expose socket.IPV6_RECVERR
pythongh-118986: expose socket.IPV6_RECVERR
gh-118986: expose `socket.IPV6_RECVERR` (#118987)
pythongh-118986: expose `socket.IPV6_RECVERR` (python#118987)