Summary: | lang/python[*]: Missing network-related constants | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Yuri Victorovich <yuri> |
Component: | Individual Port(s) | Assignee: | freebsd-python (Nobody) <python> |
Status: | Open --- | ||
Severity: | Affects Only Me | CC: | diizzy, rene, w.schwarzenfeld, yuri |
Priority: | --- | Keywords: | needs-qa |
Version: | Latest | Flags: | koobs:
maintainer-feedback+
koobs: maintainer-feedback? (yuri) |
Hardware: | Any | ||
OS: | Any |
Description
Yuri Victorovich
![]() ![]() /usr/include/netinet/in.h has #define IP_MULTICAST_LOOP 11 #define IP_ADD_MEMBERSHIP 12 IPPROTO_DIVERT is not in. but is this still relevant? (In reply to w.schwarzenfeld from comment #1) Yes, this can never become irrelevant. All network values from /usr/include/netinet/in.h need to be reflected in python (all versions). The only reason this hasn't come up much is that there is not not much software that does low-level network operations. Or, porters might just patch in ad-hoc values because it is much easier. But in the ideal world they should all be defined in python. (#define IPPROTO_DIVERT 258 is also there) Closing this PR, since it specifically only mentions lang/python34 which expired today. Valid for all versions of python. Is this still a thing in recent versions? Python-3.9 now has socket.IP_ADD_MEMBERSHIP, but socket.IPPROTO_DIVERT is still missing, and socket.IPPROTO_CARP is also missing. Probably other constants are also missing. (In reply to Yuri Victorovich from comment #6) To clarify, this is an 'upstream doesn't support certain socket options on freebsd' issue, and applies to all versions, modulo adding IP_ADD_MEMBERSHIP for 3.9+? 1) Is comment 0 a complete list of missing socket options? 2) Is there a difference in socket options between FreeBSD versions that needs to be considered? 3) Are there any additional changes/additions in 3.10+ ? Answers to those question is a good first to pushing this upstream |