citry-django
Citry and Django's template engines, composed.
from citry import Citry
from citry_django import CitryDjangoExtension
app = Citry(extensions=[CitryDjangoExtension()])
# settings.py
TEMPLATES = [{"BACKEND": "citry_django.backend.CitryTemplates", "APP_DIRS": True, ...}]
CITRY_APP = "myproject.app:app"
Any {% tag %} you can {% load %} in Django then works inside a Citry
component, and Citry components work in your existing Django templates. Neither
syntax changes, and the adapter names no tag: each engine's own parser decides
what belongs to it.
See the repository README for the full picture, the limits, and how it works.
Optional extras
pip install citry-django[compressor]
Routes each component's CSS and JS through django-compressor, so assets are
preprocessed (SCSS, Less, ...) and minified. See citry-django-compressor.
Metadata
Release files for citry-django 0.3.4
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 |
|---|---|---|---|---|
| citry_django-0.3.4.tar.gz | 29.4 kB | With provenance | Details for citry_django-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| citry_django-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for citry_django-0.3.4-py3-none-any.whl |
Total release size: 67.9 kB
Release files / citry_django-0.3.4.tar.gz
| Download URL | citry_django-0.3.4.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c366046a02c3185db063ab9892a3bbfbf9496d5865374fa23c9ceb6559a58ae8
|
|
BLAKE2b-256 checksum How to use checksums |
f419e0ff5903397acbd9044d597e138ea2b68bcc8b2648f1fdb908a053942d2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / citry_django-0.3.4-py3-none-any.whl
| Download URL | citry_django-0.3.4-py3-none-any.whl |
|---|---|
| Size | 38.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
487ee332783f85b7946133b340feed24c7009254fa0cd9f17db69957b20b41f8
|
|
BLAKE2b-256 checksum How to use checksums |
4a35f1faba47119691ea8c44de9b615aa43354e776ee6bce11ec6dc44e55042e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for citry-django 0.3.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for citry_django-0.3.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA 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.