UNKNOWN
3 maintainers
Metadata
3 maintainers
Release files for tgMochiKit 1.4.2
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 | |
|---|---|---|---|---|
| tgMochiKit-1.4.2.tar.gz | 686.4 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tgMochiKit-1.4.2-py2.5.egg | Legacy Egg format | - | - | Details |
| tgMochiKit-1.4.2-py2.4.egg | Legacy Egg format | - | - | Details |
Total release size: 2.3 MB
Release files / tgMochiKit-1.4.2.tar.gz
| Download URL | tgMochiKit-1.4.2.tar.gz |
|---|---|
| Size | 686.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc7308115c8cd587bb0ce6a300f7a9b2789eb2b3758610a835e1432bb9bbe89e
|
|
BLAKE2b-256 checksum How to use checksums |
9e52d585170bcfa2ff4d94a253749b1e5bfbde51d54a246479be25205fca9c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tgMochiKit-1.4.2-py2.5.egg
| Download URL | tgMochiKit-1.4.2-py2.5.egg |
|---|---|
| Size | 798.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
c5b6804fbd163be4b5b3c758858f5b0d2755d801b375ddbde544ed0c1795881e
|
|
BLAKE2b-256 checksum How to use checksums |
dea5f6d5c4ee537a7e8edb3840fc2cbd1e4066a2a8af17042859945d5a5d32bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tgMochiKit-1.4.2-py2.4.egg
| Download URL | tgMochiKit-1.4.2-py2.4.egg |
|---|---|
| Size | 798.3 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
70f5cb83a9d28f69bb0a284fa91e8ffd597c89d7dffdbd734395a4b6f01e1d6e
|
|
BLAKE2b-256 checksum How to use checksums |
fe01799b878a9cabf6cb3164a75edd5ed0b2f9f8e4056e55584a11a4cd3b9c49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tgMochiKit 1.4.2
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.
