Django Async is an asynchronous execution queue for Django with proper database transaction management.
Building a database backed task queue is a fairly trivial thing, but getting the database transactions exactly right is no simple matter.
Usage and documentation
All documentation can be found at http://www.kirit.com/Django%20Async
Doing development
This project uses git flow. Don’t forget to do ``git flow init -d``
To test just run tox. But if you want to go the old way then to create virtual environments for running the tests you can execute test-projects/make-virtual-environments. To run the tests execute runtests.
1 maintainer
Metadata
1 maintainer
Release files for django-async 0.7.3
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-async-0.7.3.tar.gz | 23.7 kB | Without provenance | Details |
Release files / django-async-0.7.3.tar.gz
| Download URL | django-async-0.7.3.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91c353c2dc2acde281b4b5f24877966eb63ce674e2d504a406f0bf0e75d1e5de
|
|
BLAKE2b-256 checksum How to use checksums |
e78952d23cb3269df8fc0538d55dbda77d6291b42a1c165bbc24850a6061873e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-async 0.7.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
