Metadata
1 maintainer
Release files for django-cache-url 3.4.6
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_cache_url-3.4.6.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_cache_url-3.4.6-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / django_cache_url-3.4.6.tar.gz
| Download URL | django_cache_url-3.4.6.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d030bd0c379310377772d513e6861a7a9dcc1e683049f27a9976ba5de3b5d1b9
|
|
BLAKE2b-256 checksum How to use checksums |
4c0c68a0fcc531ccdff53aba9b01d3b53208dddb646ba8f317d8b0e2e21e470c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Release files / django_cache_url-3.4.6-py2.py3-none-any.whl
| Download URL | django_cache_url-3.4.6-py2.py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
af524c2f47d753d3324a6a38a03ab8f6147b045c81cbb5ec2bfc8ecb9c95ed3c
|
|
BLAKE2b-256 checksum How to use checksums |
a2803933edc478585103ab2726eacb0dd70aec60bc4c52208e427829b9700577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.14
|
Security for django-cache-url 3.4.6
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.
