@@ -360,7 +360,7 @@ PCAPNG Support
360360**Done. ** The builtin default engine parses PCAP-NG files;
361361:class: `~pcapkit.protocols.misc.pcapng.PCAPNG ` implements the format, with its
362362block and option enumerations under :doc: `/pcapkit/const/pcapng `. This closes
363- ` #35 < https://github.com/JarryShaw/PyPCAPKit/issues/35 >`__ .
363+ :issue: ` 35 ` .
364364
365365Maybe Even Faster?
366366------------------
@@ -506,8 +506,8 @@ both of the following are worth knowing before reaching for them:
506506 ``import pcapfile `` still succeeds on 3.12+, the modules the engine
507507 actually needs raise :exc: `ModuleNotFoundError `. Upstream ``master `` (0.12.1,
508508 unreleased) has fixed this, and that is what the engine was verified against.
509- The extra therefore installs a version that only works on Python 3.10 and
510- 3.11 until 0.12.1 is published.
509+ The extra therefore installs a version that does not work on Python 3.12 or
510+ newer until 0.12.1 is published.
511511* **pypcap ** -- the 1.3.0 sdist (the only distribution; there has been no wheel
512512 since Python 2.7) ships a ``pcap.c `` pre-generated by Cython 0.29.32 and
513513 compiles it verbatim -- its :file: `setup.py ` never invokes Cython. That
@@ -1116,7 +1116,7 @@ library gets swept deliberately, in strands:
11161116* **Packet formats against the specifications. ** The most valuable strand, and
11171117 the one with the clearest evidence behind it: reading the RFC field-by-field
11181118 against the schema is what produced
1119- ` # 472 < https://github.com/JarryShaw/PyPCAPKit/issues/472 >`__ — HIP
1119+ :issue: ` 472 ` — HIP
11201120 parameters sizing their list entries at one octet where :rfc: `5770 ` §5.4 and
11211121 :rfc: `7402 ` §5.1.2 specify sixteen bits — and the same method then *cleared *
11221122 the further
@@ -1129,13 +1129,13 @@ library gets swept deliberately, in strands:
11291129 This strand has the sharpest evidence of them all, because duplication here has
11301130 already *caused * defects rather than merely offended tidiness:
11311131
1132- - ` # 487 < https://github.com/JarryShaw/PyPCAPKit/issues/487 >`__ existed because
1132+ - :issue: ` 487 ` existed because
11331133 :meth: `IPv6_Route.make() <pcapkit.protocols.internet.ipv6_route.IPv6_Route.make> `
11341134 computed ``Hdr Ext Len `` in **separate ** branches with different wrong units, and the
11351135 read side computed the inverse elsewhere with yet another. The fix was not new
11361136 arithmetic but one helper per direction, each documenting the :rfc: `8200#section-4.4 `
11371137 unit and saying what its counterpart is.
1138- - ` # 483 < https://github.com/JarryShaw/PyPCAPKit/issues/483 >`__ was the scapy
1138+ - :issue: ` 483 ` was the scapy
11391139 toolkit adapter passing a fragment offset unscaled where every sibling
11401140 adapter scaled it. Every adapter restates the same field mapping, so a
11411141 convention that holds in all but one is invisible until a capture is
0 commit comments