The sphinx-rerediraffe fork was published as a temporary solution. The changes it introduces have already been proposed upstream (sphinx-doc/sphinxext-rediraffe#67, sphinx-doc/sphinxext-rediraffe#68).
The features specific to sphinx-rerediraffe are documented in this repository’s docs/index.rst file.
sphinx-rerediraffe
Sphinx extension to redirect files
This Sphinx extension redirects non-existent pages to working pages. Rediraffe can also check that deleted or renamed files in your git repo are redirected.
Rediraffe creates a graph of all specified redirects and traverses it to point all internal urls to leaf urls. This means that chained redirects will be resolved. For example, if a config has 6 chained redirects, all 6 links will redirect directly to the final link. The end user will never experience more than 1 redirection.
Note: Rediraffe supports the html and dirhtml builders.
Installation
pip install sphinx-rerediraffe
Usage
See the documentation.
Metadata
Release files for sphinx-rerediraffe 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_rerediraffe-0.1.0.tar.gz | 25.6 kB | With provenance | Details for sphinx_rerediraffe-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_rerediraffe-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sphinx_rerediraffe-0.1.0-py3-none-any.whl |
Total release size: 34.2 kB
Release files / sphinx_rerediraffe-0.1.0.tar.gz
| Download URL | sphinx_rerediraffe-0.1.0.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5df6c3ab6fb8e0d7ff3cc441556f6125b8a58f7903185993e03c26a2b23ca68
|
|
BLAKE2b-256 checksum How to use checksums |
c9535858d87b2b202a5cadb391af710b3a2276e1c644dc1ec11c2c35a8aef636
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 4, 2026.
Transparency logRelease files / sphinx_rerediraffe-0.1.0-py3-none-any.whl
| Download URL | sphinx_rerediraffe-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f4f8907d37e1ab47ccf6d52d7836b91f10dc9c5df0aa61b43c3ce37b27f5cb4
|
|
BLAKE2b-256 checksum How to use checksums |
ad7f06af7575dc74e209cbc59776b5920bd6d524fc61b4d3fa91eebe3496fc49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 4, 2026.
Transparency logSecurity for sphinx-rerediraffe 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_rerediraffe-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 Oct 4, 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.