1 maintainer
Metadata
1 maintainer
Release files for ftrack-constants 3.0.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 | |
|---|---|---|---|---|
| ftrack_constants-3.0.0.tar.gz | 8.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftrack_constants-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.0 kB
Release files / ftrack_constants-3.0.0.tar.gz
| Download URL | ftrack_constants-3.0.0.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3cabcf93272e624acd02d669598a10a09d703701f501bc2f030c2eaf41c9d8e
|
|
BLAKE2b-256 checksum How to use checksums |
7b72bb58af125a91bd9b0bf321db8257d6d2501eae9723936425934dd57d22a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / ftrack_constants-3.0.0-py3-none-any.whl
| Download URL | ftrack_constants-3.0.0-py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a6a6e2b4a1d607d45f8800cced965d52c54d8821715937cb98a740272fa8182
|
|
BLAKE2b-256 checksum How to use checksums |
384a89fcd16461ef9fb715f467d039a54515973ba944d74f754e0c3bc336f6a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for ftrack-constants 3.0.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.
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.
