citry-django-djc
Let citry-django read Django's syntax the way django-components does.
pip install citry-django[django-components]
from citry import Citry
from citry_django import CitryDjangoExtension
from citry_django_djc import tokenize
app = Citry(extensions=[CitryDjangoExtension(tokenizer=tokenize)])
Django's own lexer ends a tag at the first %}, even one inside a quoted
argument. django-components replaces the tokenizer so a tag can carry template
source as data:
{% component "code_block" code="{% if user %}Hi{% endif %}" %}{% endcomponent %}
citry-django claims byte ranges with whichever tokenizer it was given. Hand it
this one and the two agree; without it they disagree on where that tag ends, and
you get an error.
1 maintainer
Metadata
1 maintainer
Release files for citry-django-djc 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_djc-0.3.4.tar.gz | 2.4 kB | With provenance | Details for citry_django_djc-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| citry_django_djc-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for citry_django_djc-0.3.4-py3-none-any.whl |
Total release size: 5.4 kB
Release files / citry_django_djc-0.3.4.tar.gz
| Download URL | citry_django_djc-0.3.4.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d30d5974467d52c4c4bf55a2bd5105e20060dff1d366578ec756e4a893eeca94
|
|
BLAKE2b-256 checksum How to use checksums |
066ab4299162ff05b89eb9b751ba2ae47ad9bed87077ab367ff4c79b26393371
|
| 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_djc-0.3.4-py3-none-any.whl
| Download URL | citry_django_djc-0.3.4-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d6977288e97bcab108e5eb2ec69eef8b1241e2af02bf9129b4dc3323e036942
|
|
BLAKE2b-256 checksum How to use checksums |
4c47afc0d1e1f1135a05c0f5fd53dc584786be7acbc322fe73988d1cf5bf650a
|
| 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-djc 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_djc-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.
