Release files for django-db-queue 3.3.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 | |
|---|---|---|---|---|
| django-db-queue-3.3.0.tar.gz | 14.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_db_queue-3.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.1 kB
Release files / django-db-queue-3.3.0.tar.gz
| Download URL | django-db-queue-3.3.0.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ace748ce70ea8fc3322691975f8ea3d97b05493457a155e85462c04151baf47f
|
|
BLAKE2b-256 checksum How to use checksums |
80a6ee7762e23de142f4c0cda9f5aa09c8a2bfa360348efa3169145786ea22f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.18
|
Release files / django_db_queue-3.3.0-py3-none-any.whl
| Download URL | django_db_queue-3.3.0-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52001c85e6b97d6e355817e212cbb7388f1494dfbf02ce2c8d8f1c2c493c4ebd
|
|
BLAKE2b-256 checksum How to use checksums |
f1bfac5f1a75c0390ab35f841d5aabf31d74e2622a7055d071e3665335650279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.18
|
Security for django-db-queue 3.3.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.
