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.

Release files for django-cte 4.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-cte 4.0.0
File	Size	Uploaded
django_cte-4.0.0.tar.gz	12.1 kB	Aug 31, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for django-cte 4.0.0
File	Interpreter	ABI	Platform	Reset
django_cte-4.0.0-py3-none-any.whl 13.9 kB Aug 31, 2026	Python 3	none	any	Details

Total release size:26.0 kB

Release files / django_cte-4.0.0.tar.gz

Download URL	django_cte-4.0.0.tar.gz
Size	12.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`bb8dd23c19111c1e55c19dc5ffb30abee354c3f57c869baace90131e1463d74d`
BLAKE2b-256 checksum How to use checksums	`86689d533b1fec250a0e4f659ef5116646cf9e61c353629f252cd5aa36587c56`
Upload date	Aug 31, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/dimagi/django-cte
Publishing commit: github.com/dimagi/django-cte/tree/5d705ee9784e71557a56c9c4fbcc14fd8b2308f8

Workflow

Publishing configuration: github.com/dimagi/django-cte/blob/5d705ee9784e71557a56c9c4fbcc14fd8b2308f8/.github/workflows/pypi.yml
Publishing logs: github.com/dimagi/django-cte/actions/runs/33387226740/attempts/1

Artifact

Subject: django_cte-4.0.0.tar.gz
SHA-256 checksum: bb8dd23c19111c1e55c19dc5ffb30abee354c3f57c869baace90131e1463d74d Verifying attestations

Release files / django_cte-4.0.0-py3-none-any.whl

Download URL	django_cte-4.0.0-py3-none-any.whl
Size	13.9 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`cf708d4172063d9a43b087a3d93b6d048c50a24fac46b04f45f274761af6db35`
BLAKE2b-256 checksum How to use checksums	`73373374d9a4dca2bd38806b3f00b8140bce59433e8342f2ffae166a55de8f86`
Upload date	Aug 31, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/dimagi/django-cte
Publishing commit: github.com/dimagi/django-cte/tree/5d705ee9784e71557a56c9c4fbcc14fd8b2308f8

Workflow

Publishing configuration: github.com/dimagi/django-cte/blob/5d705ee9784e71557a56c9c4fbcc14fd8b2308f8/.github/workflows/pypi.yml
Publishing logs: github.com/dimagi/django-cte/actions/runs/33387226740/attempts/1

Artifact

Subject: django_cte-4.0.0-py3-none-any.whl
SHA-256 checksum: cf708d4172063d9a43b087a3d93b6d048c50a24fac46b04f45f274761af6db35 Verifying attestations