This release is a pre-release and may not be stable for production use.
sphinxcontrib-redoc
Fork (temporary?) of sphinxcontrib-redoc that adds support for Swagger specs that use include files with relative paths.
The Sphinx extension that renders OpenAPI (fka Swagger) specs with love (❤️) using amazing ReDoc. Don’t believe it? Here’s the proof. Now stop frustrating and start moving your projects to OpenAPI and ReDoc with this small first step:
$ pip install gmlc-tdc-sphinxcontrib-redoc
Free software: BSD License
Documentation: https://sphinxcontrib-redoc.readthedocs.io
Any feedback, any contribution is really appreciated!
Metadata
Release files for gmlc-tdc-sphinxcontrib-redoc 1.6.1a1
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 |
|---|---|---|---|---|
| gmlc-tdc-sphinxcontrib-redoc-1.6.1a1.tar.gz | 349.4 kB | Without provenance | Details for gmlc-tdc-sphinxcontrib-redoc-1.6.1a1.tar.gz |
Release files / gmlc-tdc-sphinxcontrib-redoc-1.6.1a1.tar.gz
| Download URL | gmlc-tdc-sphinxcontrib-redoc-1.6.1a1.tar.gz |
|---|---|
| Size | 349.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efd9417a506e9f0a4453f133894621e835b3a6a46164d08f248b104a3250fe32
|
|
BLAKE2b-256 checksum How to use checksums |
f962b5abc72c5f2c77d4addf971d9fb876452f0132a0ba2dd79d2b47df79dc56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.7.11
|
Security for gmlc-tdc-sphinxcontrib-redoc 1.6.1a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.