Sphinx extension for masking unsupported directives and roles.
Please refer to Documentation for more details.
Metadata
Release files for sphinxnotes-mock 1.1
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 | |
|---|---|---|---|---|
| sphinxnotes_mock-1.1.tar.gz | 31.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinxnotes_mock-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 kB
Release files / sphinxnotes_mock-1.1.tar.gz
| Download URL | sphinxnotes_mock-1.1.tar.gz |
|---|---|
| Size | 31.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ff5dcac6dc565e4fb0a54707eef4e3a04165f32524631f9f654644f07138d30
|
|
BLAKE2b-256 checksum How to use checksums |
f7ea20f44b43118c7b84bbb0e038e4802ca7db48fc936463209cfc9de08bde42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / sphinxnotes_mock-1.1-py3-none-any.whl
| Download URL | sphinxnotes_mock-1.1-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72ecc8c63cfb96e1258e29aef9cb883324ad6912ee5d1adadb53f82da541c6f2
|
|
BLAKE2b-256 checksum How to use checksums |
72b8bc56c43a192b7c54b2195f916b6975976b05d1afd8fbce51a3c64b04fde0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for sphinxnotes-mock 1.1
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.