Metadata
1 maintainer
Release files for Django-SupportTools 3.6.4
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 | |
|---|---|---|---|---|
| django_supporttools-3.6.4.tar.gz | 727.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_supporttools-3.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / django_supporttools-3.6.4.tar.gz
| Download URL | django_supporttools-3.6.4.tar.gz |
|---|---|
| Size | 727.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e02271ca5cfdd9e837e17e9a2c923251d79eba8d67245c1faa371028e70f8e6
|
|
BLAKE2b-256 checksum How to use checksums |
504e772e6056567a8a56b29182fbe8ccf455f8b62bd6dad2647bcfc8b211eb1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Release files / django_supporttools-3.6.4-py3-none-any.whl
| Download URL | django_supporttools-3.6.4-py3-none-any.whl |
|---|---|
| Size | 734.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5906fb2da4ee78e010aff1fa74941eefa075a1dd9309ecf3e22a18663036fb2c
|
|
BLAKE2b-256 checksum How to use checksums |
586f1485b38b0eea4521842e1100d503c84634e381b35612f359941fab9cc661
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Security for Django-SupportTools 3.6.4
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.
