Metadata
Release files for ftrack-framework-core 3.2.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 | |
|---|---|---|---|---|
| ftrack_framework_core-3.2.1.tar.gz | 33.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftrack_framework_core-3.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 77.5 kB
Release files / ftrack_framework_core-3.2.1.tar.gz
| Download URL | ftrack_framework_core-3.2.1.tar.gz |
|---|---|
| Size | 33.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d04e730e218e34bb78024617e665c8da53797c65469901d402617e47cde89ab9
|
|
BLAKE2b-256 checksum How to use checksums |
97d970919cc25216970b35db558035ae22e88401681c06f400a2ef088f650cb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / ftrack_framework_core-3.2.1-py3-none-any.whl
| Download URL | ftrack_framework_core-3.2.1-py3-none-any.whl |
|---|---|
| Size | 44.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
895177e6d77d4e705d1d0b7e17aef376ce23ddf21a7b88917e1582085eaaa8b8
|
|
BLAKE2b-256 checksum How to use checksums |
f7d7c88093ecb516d0a42828eb73322558e3881aa1ee8d6ed64c66ec2aa8945a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for ftrack-framework-core 3.2.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.