sphinx-anchormap
A Sphinx extension providing an anchormap directive for client-side
redirects of removed HTML anchors.
When a section or description is moved or removed, old #fragment
links out in the wild break silently. anchormap lets you declare
redirect entries next to the content; they are resolved at build time,
embedded in the page as JSON, and a small script redirects visitors
from the stale anchor to its new location.
Installation
pip install sphinx-anchormap
Then in conf.py:
extensions = [
"anchor_redirects",
]
Usage
Declare redirects in the document the old anchors used to live on:
.. anchormap::
removed-anchor: :ref:`new-target`
Each entry is old-html-fragment: target. The directive produces no output;
visiting the page with #removed-anchor in the URL redirects to the new
target instead.
Metadata
Release files for sphinx-anchormap 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sphinx_anchormap-0.1.0.tar.gz | 5.9 kB | With provenance | Details for sphinx_anchormap-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_anchormap-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sphinx_anchormap-0.1.0-py3-none-any.whl |
Total release size: 10.2 kB
Release files / sphinx_anchormap-0.1.0.tar.gz
| Download URL | sphinx_anchormap-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eddb1e0bd8519179adc1a44c1bcd42b8a44cf80b7fad49d2640a9cb98064bbb4
|
|
BLAKE2b-256 checksum How to use checksums |
e0d491bf0c953685ae3daac6c1a23b5944a70181d04893d0e610d76e72fd0b85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logRelease files / sphinx_anchormap-0.1.0-py3-none-any.whl
| Download URL | sphinx_anchormap-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a50f75371f7a40f1ae02905483a5f5dc1d254e6b079a97ab35b383b1d3372409
|
|
BLAKE2b-256 checksum How to use checksums |
62b0ecbf93f6fa5f1456541702f755fb031c10143dff8f9f089dc1b5b6c7893b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logSecurity for sphinx-anchormap 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sphinx_anchormap-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.