django-signalcontrol
Django signalcontrol is a django extension for dynamically enabling/disabling signals. This application allows django signals to be disabled or enabled on-demand through the django admin interface.
Code Quality
Code Coverage Dashboard:
https://coveralls.io/github/djangoaddicts/django-signalcontrol
Documentation
Full documentation can be found on http://django-signalcontrol.readthedocs.org. Documentation source files are available in the docs folder.
License
django-signalcontrol is licensed under the GNU-3 license (see the LICENSE file for details).
https://github.com/djangoaddicts/django-signalcontrol/blob/docs/LICENSE
Installation
-
install via pip:
pip install django-signalcontrol -
add the following to your INSTALLED_APPS in settings.py:
djangoaddicts.signalcontrol
Features
Signal Decorator
SignalControl can be added to a signal with the provided decorator. In the signals.py file, import the signalcontrol decorator and add the signal_control decorator to the line directly above the signal definition.
Admin Interface
An django admin interface for django-signalcontrol is available to set signals to enabled or disabled. This displays all signals that can be controlled, and lists the application, model, signal receiver and signal name. Additionally, full search is available and filters are available for each field. Signals can be enabled or disabled individually or in bulk.
Usage Example
from signalcontrol.decorators import signal_control
@receiver(post_save, sender=MyCoolModel)
@signal_control
def msg_after_my_model_save(sender, instance, created, **kwargs):
""" some signal """
print('you just saved an instance of MyCoolModel')
Metadata
Release files for django-signalcontrol 0.1.2
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 | Actions |
|---|---|---|---|---|
| django-signalcontrol-0.1.2.tar.gz | 45.5 kB | Without provenance | Details for django-signalcontrol-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_signalcontrol-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for django_signalcontrol-0.1.2-py3-none-any.whl |
Total release size: 78.7 kB
Release files / django-signalcontrol-0.1.2.tar.gz
| Download URL | django-signalcontrol-0.1.2.tar.gz |
|---|---|
| Size | 45.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d06b8382f594aa0c211da3f586a5c8a1ca7d69aa952ffb9bed078b9f4876f49
|
|
BLAKE2b-256 checksum How to use checksums |
ce7e84ef433658439687ef6632c3dcc7fd03bd8b24539d314ea14c1a6a3ab9be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / django_signalcontrol-0.1.2-py3-none-any.whl
| Download URL | django_signalcontrol-0.1.2-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0fe2ee6ee9ed438eab3df91c39f83803dcc48fef57e22c6614017bd8dea57183
|
|
BLAKE2b-256 checksum How to use checksums |
e7cb3377be783383ed1e65ed176ee6faa1f615d488b1e5b603dd6c417dfc6fc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for django-signalcontrol 0.1.2
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.