diff options
| author | Eugene Toder <eltoder@users.noreply.github.com> | 2023-11-27 23:42:37 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-11-27 23:42:37 (GMT) |
| commit | 562d7149c6944fb9e4c7be80664b2f2d5a12a3ea (patch) | |
| tree | 3429dada42a19d49e7d6e45ea5d2bc466e0b61f2 /Python/legacy_tracing.c | |
| parent | b90a5cf11cdb69e60aed7be732e80113bca7bbe4 (diff) | |
| download | cpython-562d7149c6944fb9e4c7be80664b2f2d5a12a3ea.zip cpython-562d7149c6944fb9e4c7be80664b2f2d5a12a3ea.tar.gz cpython-562d7149c6944fb9e4c7be80664b2f2d5a12a3ea.tar.bz2 | |
Correct documentation for AF_PACKET (#112339)
Protocol in the address tuple should *not* be in the network-byte-order, because it is converted internally[1].
[1] https://github.com/python/cpython/blob/89ddea4886942b0c27a778a0ad3f0d5ac5f518f0/Modules/socketmodule.c#L2144
network byte order doesn't make sense for a python level int anyways. It's a fixed size C serialization concept.
Diffstat (limited to 'Python/legacy_tracing.c')
0 files changed, 0 insertions, 0 deletions