===================================================================
These are bindings for the `Jinja2 templating system`_ for the
``repoze.bfg`` web framework.
High-Level API
--------------
The API follows the pattern of the "default" template API for
``repoze.bfg``, which includes three functions: ``get_template``,
``render_template``, and ``render_template_to_response``. From within
a repoze.bfg view function, you might do::
from webob import Response
from repoze.bfg.jinja2 import get_template
template = get_template('templates/foo.jinja2')
return Response(template.render(foo=1))
Or::
from repoze.bfg.jinja2 import render_template
s = render_template('templates/foo.jinja2', foo=1)
return Response(s)
Or::
from repoze.bfg.jinja2 import render_template_to_response
return render_template_to_response('templates/foo.jinja2', foo=1)
All of these examples are equivalent. The first argument passed in to
each of them (representing the template location) can be either a full
system file path, or can be a file path relative to the package in
which the view function is defined (as shown above).
``repoze.bfg.jinja2`` can also act as a "renderer" for a view when its
``configure.zcml`` file is included within the ``repoze.bfg``
application you're developing::
@bfg_view(renderer='templates/foo.jinja2')
def aview(request):
return {'foo':1}
See the generated ``bfg_jinja2_starter`` paster template for an
example of using the renderer facility.
Installation
------------
Install using setuptools, e.g. (within a virtualenv)::
$ easy_install -i http://dist.repoze.org/bfg/dev/simple repoze.bfg.jinja2
Creating a Jinja2 ``repoze.bfg`` Project
----------------------------------------
After you've got ``repoze.bfg.jinja2`` installed, you can invoke the
following command to create a Jinja2-based ``repoze.bfg`` project::
$ paster create -t bin/paster create -t bfg_jinja2_starter
Reporting Bugs / Development Versions
-------------------------------------
Visit http://bugs.repoze.org to report bugs. Visit
http://svn.repoze.org to download development or tagged versions.
Changelog
=========
0.6 (2009-11-30)
----------------
- ``repoze.bfg`` 1.2 compatibility. This package is no longer
compatible with ``repoze.bfg`` 1.1
- Take out dependency on private package index in setup.cfg.
0.5 (2009-11-09)
----------------
- ``repoze.bfg`` 1.1 support including renderer support. Changed
``bfg_jinja2_starter`` paster template to generate a view that uses
a renderer.
- This version is no longer compatible with ``repoze.bfg`` 1.0.X (use
0.4 for BFG 1.0.X compatibility).
0.4 (2009-11-07)
----------------
- Respect ``reload_templates`` option in BFG.
- Don't require ez_setup.py anymore.
- Nosetests no longer does coverage by default.
- This will be the last release will be the last release that will
operate under BFG 1.0. Future versions will operate only under BFG
1.1.
0.3 (2009-05-03)
----------------
- Add a paster template for creating a Jinja2-based ``repoze.bfg``
project. (e.g. ``paster create -t bfg_jinja2_starter``).
0.2 (2009-05-02)
----------------
- Point setup.cfg index_url at http://dist.repoze.org/bfg/dev/simple
0.1 (unknown date)
------------------
- Initial release.
Metadata
Release files for repoze.bfg.jinja2 0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repoze.bfg.jinja2-0.6.tar.gz | 29.8 kB | Without provenance | Details for repoze.bfg.jinja2-0.6.tar.gz |
Release files / repoze.bfg.jinja2-0.6.tar.gz
| Download URL | repoze.bfg.jinja2-0.6.tar.gz |
|---|---|
| Size | 29.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd8a7e24b002b9fc2558aa6d7f36b5e4ac1ea46239d243a485d6fa4fc4e2d368
|
|
BLAKE2b-256 checksum How to use checksums |
71f8ddcbcdca38243c9d18d58074133fe2bf9c967e16de6aca7997f7d3d177e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repoze.bfg.jinja2 0.6
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.