Atomic transaction aware signals for Django 1.6+
Project description
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.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Hashes for django-atomic-dispatch-2.0.0.tar.gz
Algorithm | Hash digest | |
---|---|---|
SHA256 | 685ac55c0a8a0f897b54ebb6352c1ba15020ba2ddf6d82d94786dd56d07d9936 |
|
MD5 | b8d2cc2e1341139c84bdfb86b1996b24 |
|
BLAKE2b-256 | ca9d578565143c9e1c6fecdb16b594fa12d82e91ec866c15126ec97baab56918 |