The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for TracAttachmentNumMacro 0.8
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 | |
|---|---|---|---|---|
| TracAttachmentNumMacro-0.8.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| TracAttachmentNumMacro-0.8-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 5.3 kB
Release files / TracAttachmentNumMacro-0.8.tar.gz
| Download URL | TracAttachmentNumMacro-0.8.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b548f02a52e9c8cf11ca12b0a981317e328d73659d70c26cbfe8392ee74cddef
|
|
BLAKE2b-256 checksum How to use checksums |
545c4c960cd1727274a707772079093e45befa0a4ef02c63e2ecb65e9526e3e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / TracAttachmentNumMacro-0.8-py2-none-any.whl
| Download URL | TracAttachmentNumMacro-0.8-py2-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
aa02f8b79793b866e28f8e975758ad8199f06cb35fbc10a4754f4504dabd11e7
|
|
BLAKE2b-256 checksum How to use checksums |
0e98de7b52d0776d5d104945e0eb7e0f35a0d8b1c47d34799dd413489dfcf468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for TracAttachmentNumMacro 0.8
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.
