django-rq-email-backend
Requirements
Installation
Install django-rq-email-backend:
pip install django-rq-email-backendAdd django_rq to INSTALLED_APPS in settings.py:
INSTALLED_APPS = (
# other apps
'django_rq_email_backend',
)You must then set django_rq_email_backend as your EMAIL_BACKEND:
EMAIL_BACKEND = 'django_rq_email_backend.backends.RQEmailBackend'
By default django-rq-email-backend will use Django’s builtin SMTP email backend for the actual sending of the mail. If you’d like to use another backend, you may set it in RQ_EMAIL_BACKEND just like you would normally have set EMAIL_BACKEND before you were using RQ. In fact, the normal installation procedure will most likely be to get your email working using only Django, then change EMAIL_BACKEND to RQ_EMAIL_BACKEND, and then add the new EMAIL_BACKEND setting from above.
Inspiration
django-rq-email-backend was heavily influenced by:
1 maintainer
Metadata
1 maintainer
Release files for django-rq-email-backend 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 | Actions |
|---|---|---|---|---|
| django_rq_email_backend-2.0.0.tar.gz | 4.7 kB | Without provenance | Details for django_rq_email_backend-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_rq_email_backend-2.0.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for django_rq_email_backend-2.0.0-py2.py3-none-any.whl |
Total release size: 9.9 kB
Release files / django_rq_email_backend-2.0.0.tar.gz
| Download URL | django_rq_email_backend-2.0.0.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e8a6c6f492f9e78711e6b563c96f7b8feaf17c8737767a30fc68b9833e3b82f
|
|
BLAKE2b-256 checksum How to use checksums |
2494ef215f97e58dac22f1b20888193601cdb0e1aea770b16b968d345536ac8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / django_rq_email_backend-2.0.0-py2.py3-none-any.whl
| Download URL | django_rq_email_backend-2.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
402ced0d8078a856a684be37206fbfb0a6056c5bfe8a753dd7eec7fcaccca224
|
|
BLAKE2b-256 checksum How to use checksums |
a78be98a24b8611f141eb8ab78f0909ab4624cffb34f8d9515e5d85055e6a912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for django-rq-email-backend 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.
