This release is a pre-release and may not be stable for production use.
Common Table Expressions with Django
Installation
pip install django-cte
Documentation
The django-cte documentation shows how to use Common Table Expressions with the Django ORM.
Running tests
cd django-cte
uv sync
pytest
ruff check
# To run tests against postgres
psql -U username -h localhost -p 5432 -c 'create database django_cte;'
export PG_DB_SETTINGS='{
"ENGINE":"django.db.backends.postgresql_psycopg2",
"NAME":"django_cte",
"USER":"username",
"PASSWORD":"password",
"HOST":"localhost",
"PORT":"5432"}'
# WARNING pytest will delete the test_django_cte database if it exists!
DB_SETTINGS="$PG_DB_SETTINGS" pytest
All feature and bug contributions are expected to be covered by tests.
Publishing a new verison to PyPI
Push a new tag to Github using the format vX.Y.Z where X.Y.Z matches the version
in __init__.py.
A new version is published to https://test.pypi.org/p/django-cte on every push to the main branch.
Publishing is automated with Github Actions.
1 maintainer
Metadata
1 maintainer
Release files for django-cte 4.0.0.dev20261001105302
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 | |
|---|---|---|---|---|
| django_cte-4.0.0.dev20261001105302.tar.gz | 12.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_cte-4.0.0.dev20261001105302-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.5 kB
Release files / django_cte-4.0.0.dev20261001105302.tar.gz
| Download URL | django_cte-4.0.0.dev20261001105302.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
207599e9cea4aa352db39e4ddd2b0cbf2fc4fb8a06a9d6ae6299cdf6e075e2cb
|
|
BLAKE2b-256 checksum How to use checksums |
a77762325d1f613ec4cbbd5b05804b180f2abbb7e83d12f52b11b5eb02de339a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 1, 2026.
Transparency logRelease files / django_cte-4.0.0.dev20261001105302-py3-none-any.whl
| Download URL | django_cte-4.0.0.dev20261001105302-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1a53aace4be1f0a6abb28f37a4e2563b1eb436c571d15db32c137b1d2a48fae
|
|
BLAKE2b-256 checksum How to use checksums |
4221998b6488eccd4087dff1f34850ba17463252fbdc8f21e99c5f0464b6b51f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 1, 2026.
Transparency logSecurity for django-cte 4.0.0.dev20261001105302
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 django_cte-4.0.0.dev20261001105302.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 1, 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.
