JNJ provides a Jinja2-based template framework.
JNJ manages a set of jinja template/macro files with their associated media fragments (CSS and Javascript). JNJ combines the media fragments of all jinja files used by a toplevel jinja template — each toplevel jinja template loads only thse media fragments it needs.
JNJ supports the calling of jinja macros by Python code — this allows the code responding to a AJAX request to use the same jinja macros as the template that rendered the original page request.
JNJ is distributed under the conditions of the BSD 3-Clause License.
JNJ is available as a git repository. You can clone that repository with:
git clone git@codeberg.org:tanzer/tapyr.git
Reports of bugs in JNJ should be submitted to the git repository.
1 maintainer
Metadata
1 maintainer
Release files for JNJ 3.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jnj-3.11-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Release files / jnj-3.11-py2.py3-none-any.whl
| Download URL | jnj-3.11-py2.py3-none-any.whl |
|---|---|
| Size | 213.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5d7b3e7d6a7256c51bbe7afe25827119fd13b4199c6dea710f8a8af922ec89a4
|
|
BLAKE2b-256 checksum How to use checksums |
f6a9d106ea61c6678ea8bdda5832976d84cc37c161f2aa77797c6ba2ae68625d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for JNJ 3.11
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.
