Render a particular block from a template to a string.
Project description
Django Render Block
Render the content of a specific block tag from a Django template. Works for arbitrary template inheritance, even if a block is defined in the child template but not in the parent. Generally it works like render_to_string from Django, but allows you to specify a block to render.
Features
Render a specific block from a template
Fully supports the Django templating engine
Partially supports the Jinja2 engine: it does not currently process the extends tag.
Requirements
Django Render Block supports Django 2.2, 3.0, and 3.1 on Python 3.6, 3.7, 3.8, and 3.9.
Examples
In test1.html:
{% block block1 %}block1 from test1{% endblock %}
{% block block2 %}block2 from test1{% endblock %}
In test2.html:
{% extends 'test1.html' %}
{% block block1 %}block1 from test2{% endblock %}
And from the Python shell:
>>> from render_block import render_block_to_string
>>> print render_block_to_string('test2.html', 'block1')
u'block1 from test2'
>>> print render_block_to_string('test2.html', 'block2')
u'block2 from test1'
It can also accept a context as a dict (just like render_to_string), in test3.html:
{% block block3 %}Render this {{ variable }}!{% endblock %}
And from Python:
>>> print render_block_to_string('test3.html', 'block3', {'variable': 'test'})
u'Render this test!'
API Reference
The API is simple and attempts to mirror the built-in render_to_string API.
render_block_to_string(template_name, block_name, context=None, request=None)
- template_name
The name of the template to load and render. If it’s a list of template names, Django uses select_template() instead of get_template() to find the template.
- block_name
The name of the block to render from the above template.
- context
A dict to be used as the template’s context for rendering. A Context object can be provided for Django templates.
context is optional. If not provided, an empty context will be used.
- request
The request object used to render the template.
request is optional and works only for Django templates. If both context and request are provided, a RequestContext will be used instead of a Context.
Exceptions
Like render_to_string this will raise the following exceptions:
- TemplateDoesNotExists
Raised if the template(s) specified by template_name cannot be loaded.
- TemplateSyntaxError
Raised if the loaded template contains invalid syntax.
There are also two additional errors that can be raised:
- BlockNotFound
Raised if the block given by block_name does not exist in the template.
- UnsupportedEngine
Raised if a template backend besides the Django backend is used.
Contributing
If you find a bug or have an idea for an improvement to Django Render Block, please file an issue or provide a pull request! Check the list of issues for ideas of what to work on.
Attribution
This is based on a few sources:
Originally Django Snippet 769
Updated version Django Snippet 942
A version of the snippets was ported as Django-Block-Render
Additionally inspired by part of django-templated-email
Also based on a StackOverflow answer 2687173
Changelog
0.8 (October 6, 2020)
render_block_to_string now forwards the Context passed as context parameter. (#21, by @bblanchon)
Drop support for Python 3.5, officially support Python 3.9.
0.7 (July 13, 2020)
Drop support for Django < 2.2.
Officially support Django 3.0, 3.1.
Drop support for Python 2.7.
Officially support Python 3.8.
0.6 (May 8, 2019)
Supports Django 1.11, Django 2.1, and Django 2.2.
Supports Python 2.7, 3.5, 3.6, and 3.7.
render_block_to_string now optionally accepts a request parameter. If given, a RequestContext instead of a Context is used when rendering with the Django templating engine. See #15, thanks to @vintage.
0.5 (September 1, 2016)
Fixes a major issue with inheriting templates and rendering a block found in the parent template, but overwriting part of it in the child template. (#8)
0.4 (August 4, 2016)
0.3.1 (June 1, 2016)
Refactoring to make more generic (for potentially supporting multiple templating engines).
0.3 (May 27, 2016)
Largely rewritten.
Updated to support modern Django (1.8, 1.9):
Guards against different template backends.
Uses internal APIs for each node.
Removed context_instance parameter.
Support for calling {{ block.super }}.
0.2.2 (January 10, 2011)
Updated per comment 3466 on Django Snippet 942 to fix an issue with nested extends. The specific bug was not reproducible, but the additional code shouldn’t hurt.
0.2.1 (August 27, 2010)
Updated per comment 3237 on Django Snippet 942 to remove a pointless render. The specific bug was not reproducible, but the code is extraneous.
0.2 (August 4, 2008)
Updated version from Django Snippet 942 by zbyte64.
Improves include:
Simpler/better handling of “extends” block tag
Searches If/Else blocks
Less code
Allow list of templates to be passed which is closer to the behavior of render_to_response
0.1 (May 22, 2008)
Initial version from Django Snippet 769 by sciyoshi.
Supports Django 0.96.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for django_render_block-0.8-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 0dc3e0f9d81c6ce5296735cf5fdd32f170d6713ece4f4f96bcef5981c997115e |
|
MD5 | a7f86c5529e5873cff2fa351c44d8499 |
|
BLAKE2b-256 | 1d9454f3f43f9eaf1b5df17c434fa8880976b6f3c534d19670a8b0d42cb035fa |