django_atomic_signals - Signals for atomic transaction blocks in Django
Don’t Use This Package
When this library was created, there was an unmet demand for its main use case: being able to run code when the current transaction commits, and only if it commits. However, signals are not the best way to do this, as Django core developer Aymeric Augustin has covered on his django-transaction-signals project (which is very similar to this one). You can read more explanation and history there.
If you want a supported method of running a function on commit, 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)
For other usecases, read Aymeric’s description of possible solutions.
If your project is still using this library, please migrate.
The current version of django-atomic-signals, 2.0.0, simply errors upon import, directing you here.
Metadata
Release files for django-atomic-signals 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-signals-2.0.0.tar.gz | 3.2 kB | Without provenance | Details |
Release files / django-atomic-signals-2.0.0.tar.gz
| Download URL | django-atomic-signals-2.0.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9fa910916fe0c7eaa2dde64a24c1f39d327347b7a9edd525d01642f303513cb
|
|
BLAKE2b-256 checksum How to use checksums |
79c69ea78282e2ed3c7295a05be5b52e219ed3c25adf39bd5bdb3d902b8819a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-atomic-signals 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.