This project has been archived by its maintainers, and is no longer receiving any updates.
django_atomic_dispatch - Atomic transaction aware signals for Django
Don’t Use This Library
This library uses django-atomic-signals. Unfortunately that library is deprecated, and is a bit too hacky. There is plenty of extra description why on django-atomic-signals’ README, and also on the similar library django-transaction-signals, by Django core developer Aymeric.
If you want a supported method of executing a signal dispatch only when the current transaction commits, then:
on Django >= 1.9, use the built-in on_commit hook
on Django < 1.9, use django-transaction-hooks (the original source of 1.9’s on_commit)
Both give examples so you are in good hands. In most cases you will just need to use a regular signal and make its send() happen inside a lambda that is passed to on_commit.
If your project is still using this library, please migrate. You will need to remove django-atomic-signals as well as django-atomic-dispatch.
The current version of django-atomic-dispatch, 2.0.0, simply errors upon import, directing you here.
2 maintainers
Metadata
2 maintainers
Release files for django-atomic-dispatch 2.0.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-atomic-dispatch-2.0.0.tar.gz | 3.2 kB | Without provenance | Details |
Release files / django-atomic-dispatch-2.0.0.tar.gz
| Download URL | django-atomic-dispatch-2.0.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
685ac55c0a8a0f897b54ebb6352c1ba15020ba2ddf6d82d94786dd56d07d9936
|
|
BLAKE2b-256 checksum How to use checksums |
ca9d578565143c9e1c6fecdb16b594fa12d82e91ec866c15126ec97baab56918
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-atomic-dispatch 2.0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
