Metadata
Release files for ftrack-framework-qt 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_framework_qt-3.0.0.tar.gz | 8.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftrack_framework_qt-3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.4 kB
Release files / ftrack_framework_qt-3.0.0.tar.gz
| Download URL | ftrack_framework_qt-3.0.0.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0cbbcaa00aad5ac869d4af4898c28f8a7228f43be7ac45c3c52fd54f83ba316b
|
|
BLAKE2b-256 checksum How to use checksums |
5c79423c8f770e464330d6c4851689d9e2ff59c2804ec27ab0d182a66432717e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / ftrack_framework_qt-3.0.0-py3-none-any.whl
| Download URL | ftrack_framework_qt-3.0.0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
241dd8820a8ead4514d088a27403c7126919349d4798345b7ace4ca7eb3988fe
|
|
BLAKE2b-256 checksum How to use checksums |
27c60024ad27104ba1e017a10106055bccb15c908f5dda7afdfdf03d3b570bc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for ftrack-framework-qt 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.