Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 545107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T10:43:35+00:00 2026-05-13T10:43:35+00:00

As we all know (or should), you can use Django’s template system to render

  • 0

As we all know (or should), you can use Django’s template system to render email bodies:

def email(email, subject, template, context):
    from django.core.mail import send_mail
    from django.template import loader, Context

    send_mail(subject, loader.get_template(template).render(Context(context)), 'from@domain.com', [email,])

This has one flaw in my mind: to edit the subject and content of an email, you have to edit both the view and the template. While I can justify giving admin users access to the templates, I’m not giving them access to the raw python!

What would be really cool is if you could specify blocks in the email and pull them out separately when you send the email:

{% block subject %}This is my subject{% endblock %}
{% block plaintext %}My body{% endblock%}
{% block html %}My HTML body{% endblock%}

But how would you do that? How would you go about rendering just one block at a time?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T10:43:35+00:00Added an answer on May 13, 2026 at 10:43 am

    This is my third working iteration. It assuming you have an email template like so:

    {% block subject %}{% endblock %}
    {% block plain %}{% endblock %}
    {% block html %}{% endblock %}
    

    I’ve refactored to iterate the email sending over a list by default and there are utility methods for sending to a single email and django.contrib.auth Users (single and multiple). I’m covering perhaps more than I’ll sensibly need but there you go.

    I also might have gone over the top with Python-love.

    def email_list(to_list, template_path, context_dict):
        from django.core.mail import send_mail
        from django.template import loader, Context
    
        nodes = dict((n.name, n) for n in loader.get_template(template_path).nodelist if n.__class__.__name__ == 'BlockNode')
        con = Context(context_dict)
        r = lambda n: nodes[n].render(con)
    
        for address in to_list:
            send_mail(r('subject'), r('plain'), 'from@domain.com', [address,])
    
    def email(to, template_path, context_dict):
        return email_list([to,], template_path, context_dict)
    
    def email_user(user, template_path, context_dict):
        return email_list([user.email,], template_path, context_dict)
    
    def email_users(user_list, template_path, context_dict):
        return email_list([user.email for user in user_list], template_path, context_dict)
    

    As ever, if you can improve on that, please do.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

There are many things that all programmers should know, but I am particularly interested
Are there any open-source libraries that all programmers should know about? I'm thinking something
What are all the common undefined behaviours that a C++ programmer should know about?
I know that I should put all the html elements in body tag, but
I don't know if I should test my @Entity-annotated Pojos. After all, there are
First of all, I don't know if this should stay in SO or go
I know there is a standard behind all C compiler implementations, so there should
we all know that the cell in uitableview can be resued, but i am
We all know how to use <ctrl>-R to reverse search through history, but did
I know there are a few questions regarding the libraries you can use to

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.