- Rename "master" git branch to "main"
- Add Python 3.11 and 3.12 support.
- Replace usage of private Pyramid APIs.
- Add
jinja2.i18n_extension
configuration setting. See #165
- Support Jinja2 >= 3.0.
- Only import
jinja2.pass_context
if available on Jinja2 >= 3.0, otherwise fallback tojinja2.contextfilter
. See #164
This release has been yanked and is no longer available.
- Fix package metadata. No changes from 2.9.
This release has been yanked and is no longer available.
- Drop Python 3.6 support.
- Add Python 3.9 and 3.10 support.
- Refactor project structure to make wheel distribution smaller.
- Blackify the codebase.
- Use the newer
@jinja2.pass_context
in favor of the deprecated@jinja2.contextfilter
. See #159
- Drop Python 3.3 support.
- Add Python 3.6 and 3.7 support.
- Support the
mapping
argument in the injectedgettext
function. See #143
- Drop Python 2.6 and 3.2 support.
- Add Python 3.5 support.
- #123: Switch to pytest and pip for testing and installation in the documentation and scaffold. nose and coverage are still used in the core pyramid_jinja2 package [stevepiercy].
- Prefer
resource_url
over deprecatedmodel_url
. Pyramid has changed its vocabulary, so let's reflect the changes. [Mikko Ohtamaa] - Support a dotted path to a gettext wrapper for the
jinja2.i18n.gettext
setting. [mmerickel]
- Officially drop support for Python 3.2, test under Python 3.5 and pypy3 [Domen Kozar]
- Don't include .pyc in wheel file [Domen Kozar]
- #116: Update scaffold to be consistent with Pyramid's default scaffolds [stevepiercy]
- #106: Allow specifying a custom pyramid_jinja.i18n.GetTextWrapper [dstufft]
- #105: Support
jinja2.finalize
configuration setting. [dstufft] - #94: Fix loading of templates with relative names on Windows [zart]
- Support Python 3.4 [mmerickel]
- Improve scaffold [marioidival]
- #98: Avoid get_current_request where possible [housleyjk]
- #99: Add resource_path filter [javex]
- #91: Fix a recursion error while attempting to include a template with the same name as one of the parents that was already loaded. [mmerickel]
- Fix 2.3.1 brownbag release. It had some erroneous didn't-mean-to-push changes that are now solved. Brought coverage back up to 100%.
- Improve the template-relative searchpath logic to search more possibilities in the include-chain built up from templates including or extending other templates. The logic for when the chain was longer than just one template including another template was broken.
- Require
pyramid_jinja2
to be included even when usingpyramid_jinja2.renderer_factory
. It is now a thin wrapper around the default renderer and can be used to share the same settings with another file extension. [mmerickel]
pyramid_jinja2
must be included into theConfigurator
in order to usepyramid_jinja2.renderer_factory
otherwise you may see the exception:ValueError: As of pyramid_jinja2 2.3, the use of the "pyramid_jinja2.renderer_factory" requires that pyramid_jinja2 be configured via config.include("pyramid_jinja2") or the equivalent "pyramid.includes" setting.
The fix is to include
pyramid_jinja2
:config.include("pyramid_jinja2")
- #88: Formalize template loading order and allow all lookups to fallback to the search path. A template is now always searched for relative to its parent template. If not found, the lookup will fallback to the search path. [mmerickel]
- Add
prepend
option toconfig.add_jinja2_search_path
to allow prepending of paths to the beginning of the search path if a path should override previously defined paths. [mmerickel]
- The 2.0 series started adding the package that invoked
config.add_jinja2_renderer
to the template search path. This is being removed in favor of explicit search paths and will hopefully not affect many people as it has only been available for a couple weeks. The only automatic search path left is the one added by the default.jinja2
renderer created when includingpyramid_jinja2
. [mmerickel] - Adjust the
config.include("pyramid_jinja2")
to add any packages fromjinja2.directories
before the default search path at the base of the app. Previously there was no way to override that search path. [mmerickel]
- The path of the child template is always considered when inheriting from
a base template. Therefore when doing
render("templates/foo.jinja2")
andfoo.jinja2
has an{% extends "base.jinja2" %}
, the template will be searched for as"templates/base.jinja2"
on the search path. Previously the path of the child template was ignored when doing the lookup for the base, causing some very subtle and unrecoverable lookup errors when the child template was found relative to the caller instead of being found on the search path. [mmerickel] - This release restores the default search path behaviors from the 1.x series that were inadvertently removed in the 2.x. The project's root package is added to the search path by default. [mmerickel]
- #86: Fix a regression caused by the new support for extending a template
relative to itself. Using
{% extends "some_asset:spec.jinja2" %}
was no longer working and is now fixed. [mmerickel]
Claim Python 3.4 support [mmerickel]
#75: Fix the missing piece of relative template loading by allowing a template to inherit from a template relative to itself, instead of forcing the parent to be on the search path. [mmerickel]
#73: Added a new
config.add_jinja2_renderer
API that can create and override multiple Jinja2 renderers, each loaded using potentially different settings and extensions.The other APIs are now keyed on the renderer extension, as each extension may have different settings. Thus
config.add_jinja2_search_path
,config.add_jinja2_extension
, andconfig.get_jinja2_environment
accept aname
argument, which defaults to.jinja2
.This deprecates the old
pyramid_jinja2.renderer_factory
mechanism for adding renderers with alternate extensions.Configuration of the renderers has been updated to follow Pyramid's standard mechanisms for conflict detection. This means that if two modules both try to add a renderer for the
.jinja2
extension, they may raise a conflict or the modifications made by the invocation closest to theConfigurator
in the call-stack will win. This behavior can be affected by callingconfig.commit
at appropriate times to force a configuration to take effect immediately. As such, configuration is deferred until commit-time, meaning that it is now possibleconfig.get_jinja2_environment
will returnNone
because the changes have not yet been committed. [mmerickel]
- The creation and configuration of the Jinja2
Environment
is now deferred until commit-type in the PyramidConfigurator
. This means thatconfig.get_jinja2_environment
may returnNone
. To resolve this, invokeconfig.commit()
before attempting to get the environment.
- #77: Change semantics of
jinja2.bytecode_caching
setting. The new default is false (no bytecode caching) --bytecode_caching
must explicitly be set to true to enable a filesystem bytecode cache. In addition, an atexit callback to clean the cache is no longer registered (as this seemed to defeat most of the purpose of having a bytecode cache.) Finally, a more complex bytecode cache may be configured by settingjinja2.bytecode_caching
directly to ajinja2.BytecodeCache
instance. (This can not be done in a paste .ini file, it must be done programatically.) [dairiki] - prevent error when using python setup.py bdist_wheel [msabramo]
- fix indentation level for Jinja2ProjectTemplate in scaffolds/__init__.py [Bruno Binet]
- Remove unnecessary dependency on
pyramid.interfaces.ITemplateRenderer
which was deprecated in Pyramid 1.5. [mmerickel] - #68: Added model_path_filter, route_path_filter and static_path_filter filters [Remco]
- #74: Fixed issue with route being converted as_const by jinja2 engine when using btyecode cache [Remco]
- #70: Do not pin for py3.2 compatibility unless running under py3.2 [dairiki]
- #56: python3.3: Non-ASCII characters in changelog breaks pip installation [Domen Kozar]
- #57: Remove useless warning: DeprecationWarning: reload_templates setting is deprecated, use pyramid.reload_templates instead. [Marc Abramowitz]
- Set jinja2.i18n.domain default to the package name of the pyramid application. [Domen Kozar]
- Add jinja2.globals setting to add global objects into the template context [Eugene Fominykh]
- Add jinja2.newstyle setting to enable newstyle gettext calls [Thomas Schussler]
Add pyramid.reload_templates to set jinja2.auto_reload instead of using reload_templates. Deprecate the latter. [Domen Kozar]
Clear bytecode cache on atexit [Domen Kozar]
Add support for more Jinja2 options. Note support for jinja2.autoescape is limited to boolean only.
- jinja2.block_start_string
- jinja2.block_end_string
- jinja2.variable_start_string
- jinja2.variable_end_string
- jinja2.comment_start_string
- jinja2.comment_end_string
- jinja2.line_statement_prefix
- jinja2.line_comment_prefix
- jinja2.trim_blocks
- jinja2.newline_sequence
- jinja2.optimized
- jinja2.cache_size
- jinja2.autoescape
[Michael Ryabushkin]
- Add jinja2.undefined setting to change handling of undefined types. [Robert Buchholz]
- Remove redundant decoding error handling [Domen Kozar]
- Configure bytecode caching by default. Introduce jinja2.bytecode_caching and jinja2.bytecode_caching_directory settings. [Domen Kozar]
- Allow to add custom Jinja2 tests in jinja2.tests setting. [Sebastian Kalinowski]
- Fix brown-bag release [Domen Kozar]
- Correctly resolve relative search paths passed to
add_jinja2_search_path
andjinja2.directories
[Domen Kozar] - #34: Don't recreate
jinja2.Environment
foradd_jinja2_extension
[Domen Kozar] - Drop Python 2.5 compatibility [Domen Kozar]
- Addition of
static_url
filter. - Add
dev
anddocs
setup.py aliases (ala Pyramid). - Changed template loading relative to package calling the renderer so it works like the Chameleon template loader.
- Make scaffolding compatible with Pyramid 1.3a2+.
- Make tests pass on Pyramid 1.2dev.
- Make compatible with Python 3.2 (requires Pyramid 1.3dev+).
- Add
get_jinja2_environment
directive. - Add all configurator directives to documentation.
- Message domain can now be specified with jinja2.i18n.domain for i18n
- Paster template now sets up starter locale pot/po/mo files
- pyramid_jinja2 now depends on Jinja2 >= 2.5.0 due to
jinja2.Environment.install_gettext_callables
use #21 - Added demo app just to visualize i18n work
jinja2.ext.i18n
is now added by default, seei18n.rst
for details- Added
add_jinja2_extension
directive to the Configurator - Updated jinja2.extensions parsing mechanism
- Fixed docs to indicate using asset: prefix is no longer necessary
- Asset-based loading now takes precedance and does not require "asset:" prefix
- Fixed the "current" package mechanism of asset: loading so that it more accurately finds the current package
- Dependency on
pyramid_zcml
removed.
- Documentation overhauled.
- Templates can now be looked up by asset spec completely bypassing
the search path by specifying a prefix of
asset:
. - Updated paster template to more closely relate to changes made to paster templmates in Pyramid core.
- Add new directive
add_jinja2_search_path
to the configurator whenincludeme
is used.
- Add
includeme
function (meant to be used viaconfig.include
). - Fix documentation bug related to
paster create
reported at #12 - Depend upon Pyramid 1.0a10 + (to make ZCML work).
- Changes to normalize with default templates shipping with Pyramid core:
remove calls to
config.begin()
andconfig.end()
from__init__.main
, entry point name changed tomain
, entry__init__.py
function name changed tomain
, depend on WebError, usepaster_plugins
argument to setup function in setup.py, depend on Pyramid 1.0a6+ (useconfig
rather thanconfigurator
).
- Use
testing.setUp
andtesting.tearDown
rather than constructing a Configurator (better fwd compat).
- Add
model_url
androute_url
filter implementations (and documented).
- Use Makefile which pulls in Pylons theme automagically.
- Add
jinja2.filters
andjinja2.extensions
settings (thanks to aodag). - Document all known settings.
- Template autoreloading did not function, even if
reload_templates
was set toTrue
.
- First release. Not backwards compatible with
repoze.bfg.jinja2
: we use a filesystem loader (the directories to load from come from thejinja2.directories
setting). No attention is paid to the current package when resolving a renderer= line.