Sphinx .NET domain
Domain to support .NET languages.
Metadata
Release files for sphinxcontrib-dotnetdomain 0.4
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 | |
|---|---|---|---|---|
| sphinxcontrib-dotnetdomain-0.4.tar.gz | 7.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinxcontrib_dotnetdomain-0.4-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 16.4 kB
Release files / sphinxcontrib-dotnetdomain-0.4.tar.gz
| Download URL | sphinxcontrib-dotnetdomain-0.4.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c41bf7a9627f0b804be1992c4b62cbf4c757d26ff7d2541eb13f68981b180073
|
|
BLAKE2b-256 checksum How to use checksums |
8df4bc8764bb2a04ba542d6145c0be145d7bf752911312c8f98ad35f138678de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / sphinxcontrib_dotnetdomain-0.4-py2-none-any.whl
| Download URL | sphinxcontrib_dotnetdomain-0.4-py2-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
985cfdba4bf67bd5af736bab76e9f206ae987c64198e6d42c7043cde11dfc374
|
|
BLAKE2b-256 checksum How to use checksums |
ddcc27c8ec33158de828d5ced6a7530dcd0aac1b953b385bd4285a9bdea38e5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sphinxcontrib-dotnetdomain 0.4
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.