NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #4005 most downloaded on PyPI
Simple reuse of partial HTML page templates in the Jinja template language for Python web frameworks.
Latest stable
0.4.0
Last release 15 days ago
07 Nov 2026
Release timing varies
gaps range from 2 months to 2.1 years
Nearly every release is documented
notes for 8 of 8 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
8 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
Nested partials in async apps (Quart, FastAPI, Starlette, and async Jinja2 environments) no longer deadlock the render thread pool. A nested render_pa
render_partial call used to wait on the same pool its outer partial was occupying, so nesting as deep as max_workers, or enough concurrent requests with nested partials, hung every request. Nested renders now run on their own short-lived thread, and nesting depth no longer counts against max_workers.enable_async=True Jinja2) now raises RecursionError at MAX_NESTED_RENDERS (100) levels, as a sync environment already did on its own. Each nested async render runs on its own thread with its own event loop, so Python's recursion limit never applied; the render kept creating threads, each slower than the last and holding file descriptors, until the process ran out... segments, leading whitespace, absolute paths, backslashes, directory names) raise TemplateNotFound on every registration path. Jinja's loader already refused them; the tests pin that the built-in renderers pass names to it untouched.llms-full.txt.skills/jinja-partials/SKILL.md that documents the rules of the package (explicit data flow, markup defaults, Starlette argument order, the async page-level rule, registration once) rather than only its API names.PartialsJinjaExtension on Flask: only context processors and the template_rendered signal are skipped inside partials; g, request, and session remain available.scripts/build_docs.py now fails when llms.txt, llms-full.txt, or the skill files are missing from the build output, or when llms-full.txt has no user guide section.scripts/postprocess_site.py repairs two more output bugs: the **data parameter rendered as data: Any = {} in the render_partial signatures, and parameter defaults wrapped in nested backticks in the Markdown reference companions.generate_render_partial now says that a custom renderer is responsible for refusing names that leave its templates folder, and the user guide explains how to let a request choose a partial safely (map the value to a name you wrote).Your coding agent can read these notes before it upgrades. Set up the MCP server →
Async executor lifecycle is now exception-safe and re-entrant. Apps registered with register_fastapi_extensions, register_starlette_extensions, or reg
register_fastapi_extensions, register_starlette_extensions, or register_quart_extensions can now start and stop repeatedly (e.g. multiple TestClient cycles) without failing, and an exception during a wrapped lifespan no longer leaks the executor (#14).max_workers, instead of degrading to a shared 4-worker pool.enable_async=True environments and render pages via render_async, exercising the executor lifecycle.register_quart_extensions(app, max_workers) - Lifecycle-managed registration for Quart apps
register_quart_extensions(app, max_workers) - Lifecycle-managed registration for Quart appsregister_fastapi_extensions(app, templates, max_workers) - Lifecycle-managed registration for FastAPI appsregister_starlette_extensions(templates, app, max_workers) - Optional app parameter for lifecycle managementexamples/ directoryrender_partial in async environmentsenable_async=True now render correctly via ThreadPoolExecutorexample/ renamed to examples/ with multiple framework examplesPartialsJinjaExtension: Added a declarative Jinja2 extension for easy integration of partials and templates. Thank you @jenisys!
Since 285d147a (15 commits)
__all__ import list to include version information, making it
easier to manage updates.Solves #9 requirements.txt details not added to setup.py.
Solves #9 requirements.txt details not added to setup.py.
This release adds a register_environment(environment) method to allow using partials with Jinja outside of a web framework like Flask. See #4 for deta
This release adds a register_environment(environment) method to allow using partials with Jinja outside of a web framework like Flask. See #4 for details. Thank you to @sam-kleiner for this feature.
2024-02-02 · GitHub
This release adds a register_environment(environment) method to allow using partials with Jinja outside of a web framework like Flask. See #4 for details. Thank you to <span class="citation" cites="sam-kleiner">@sam-kleiner</span> for this feature.
Published to PyPI on 2021-12-14.
Published to PyPI on 2021-12-14.
render_partial and generate_render_partial accept a custom renderer, and Flask is no longer required.include and macro.This GitHub release was created after the fact to match the version on PyPI.
Initial release of jinja-partials, published to PyPI on 2021-07-26.
Initial release of jinja-partials, published to PyPI on 2021-07-26.
render_partial() Jinja global, so HTML fragments can be composed and nested with explicitly passed data.jinja_partials.register_extensions(app).This GitHub release was created after the fact to match the version on PyPI.
One column per quarter.