Skip to main content

Django Email Tools

CircleCI Coverage Status PyPi Package

Requirements

  • Python 3.6+
  • Django 2.2+

Installation

Install with pip pip install django-email-tools

Add email_tools to INSTALLED_APPS

INSTALLED_APPS = (
    ...
    'email_tools.apps.EmailToolsConfig',
    ...
)

Add something like the following to urls.py

if settings.DEBUG:
    urlpatterns = [
        path("emailpreview/", include("email_tools.urls", namespace="email_tools")),
    ] + urlpatterns

Documentation

All settings are handled within a EMAIL_TOOLS dictionary.

Example:

PLATFORM_ACCOUNTS = {
    'FROM_EMAIL': 'example@example.com',
    'TEMPLATE_DIRECTORY': os.path.join(settings.BASE_DIR, "templates", "emails"),
}

The available settings are:

FROM_EMAIL the email to send from.

TEMPLATE_DIRECTORY the path to a directory containing .html files used in emails.

Usage

Django Email Tools contains two main parts.

First, is email_tools.emails.send_email a utility to send html emails given a django template and context.

The second is a debugging page that allows you to see what the rendered result of an email template would look like. This page also allows you to get a list of variables used by the template and modify those variables and see results in real-time.

Changelog

See CHANGELOG.md

License

See LICENSE

Metadata

Release files for django-email-tools 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-email-tools 0.1.1
File Size Uploaded Provenance
django-email-tools-0.1.1.tar.gz 6.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for django-email-tools 0.1.1
File Interpreter ABI Platform
django_email_tools-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 14.2 kB

Release files / django-email-tools-0.1.1.tar.gz

Download URL django-email-tools-0.1.1.tar.gz
Size 6.3 kB
Tags Source
SHA-256 checksum
How to use checksums
2d14ab510dcb3f9b46865f6f55dcc171ff49b2e0406b5cf7a66efd58ee670aac
BLAKE2b-256 checksum
How to use checksums
f623695cd19322315ffa73d5d2cf6d74ac84cd1b00e0a1d69370f3c963c5d50f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.8.0 tqdm/4.48.0 CPython/3.7.8

Release files / django_email_tools-0.1.1-py3-none-any.whl

Download URL django_email_tools-0.1.1-py3-none-any.whl
Size 7.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
08781bbb6a828352489d5945a734c0143b80b61160ecbf079f95c272a9a93437
BLAKE2b-256 checksum
How to use checksums
4e06941f4a6f5665d38240be78d086e3ca1b38fd1fbff1d2fde34b4028936973
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.2.0 requests-toolbelt/0.8.0 tqdm/4.48.0 CPython/3.7.8

Security for django-email-tools 0.1.1

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.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page