This release is a pre-release and may not be stable for production use.
UNKNOWN
1 maintainer
Metadata
1 maintainer
Release files for twAjaxTools 0.1a0dev-r2998
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 | |
|---|---|---|---|---|
| twAjaxTools-0.1a0dev-r2998.zip | 21.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| twAjaxTools-0.1a0dev_r2998-py2.4.egg | Legacy Egg format | - | - | Details |
Total release size: 45.9 kB
Release files / twAjaxTools-0.1a0dev-r2998.zip
| Download URL | twAjaxTools-0.1a0dev-r2998.zip |
|---|---|
| Size | 21.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e9477ef7ac5d960d21595f2dc2df147091e3a70901e88b2b08a62e69b10b373
|
|
BLAKE2b-256 checksum How to use checksums |
c512461ed1bb02b6d9c3e2ab04100b0339741e0b0f8701e4048ac1a89ce90888
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / twAjaxTools-0.1a0dev_r2998-py2.4.egg
| Download URL | twAjaxTools-0.1a0dev_r2998-py2.4.egg |
|---|---|
| Size | 24.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
5f2a347fe1310886e0c8aea3329687d833c595340b783428ca9fedf5f84f2826
|
|
BLAKE2b-256 checksum How to use checksums |
00cad418d6961fcb7b3d688157bcc765d2307bd443bf37584be52ed3892721a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for twAjaxTools 0.1a0dev-r2998
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.
