Pre-release

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.

Metadata

Release files for django-cte 4.0.0.dev20261027102036

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.dev20261027102036
File	Size	Uploaded	Provenance	Actions
django_cte-4.0.0.dev20261027102036.tar.gz	12.5 kB	Oct 27, 2026	With provenance	Details for django_cte-4.0.0.dev20261027102036.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for django-cte 4.0.0.dev20261027102036
File	Interpreter	ABI	Platform	Actions Reset
django_cte-4.0.0.dev20261027102036-py3-none-any.whl 14.1 kB Oct 27, 2026 With provenance	Python 3	none	any	Details for django_cte-4.0.0.dev20261027102036-py3-none-any.whl

Total release size: 26.6 kB

Release files / django_cte-4.0.0.dev20261027102036.tar.gz

Download URL	django_cte-4.0.0.dev20261027102036.tar.gz
Size	12.5 kB
Tags	Source
SHA-256 checksum How to use checksums	`f5680339a6797dd66b55c7d8e2e1c88b6bf7487b24e1e1fe8ba7b80df2908a63`
BLAKE2b-256 checksum How to use checksums	`344543b467e47d5800f7850905e3cb3475178867799d64c4148c44a6e7ebf88c`
Upload date	Oct 27, 2026
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.

Identity

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

Workflow

Publishing configuration: github.com/dimagi/django-cte/blob/7afdb68f9db99da8e37d39940f28c244010061c8/.github/workflows/pypi.yml
Publishing logs: github.com/dimagi/django-cte/actions/runs/40487666280/attempts/1

Artifact

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

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

Download URL	django_cte-4.0.0.dev20261027102036-py3-none-any.whl
Size	14.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`0da71dc1d53f5bc319e1a0460b9fab255fc7cb8303020b2c81f26093cdd6f310`
BLAKE2b-256 checksum How to use checksums	`4d81754115d14f3f139c75f26097191dcbaed36ce1cf5b18f8143fe4be8606c3`
Upload date	Oct 27, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.16`

Provenance

Identity

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

Workflow

Publishing configuration: github.com/dimagi/django-cte/blob/7afdb68f9db99da8e37d39940f28c244010061c8/.github/workflows/pypi.yml
Publishing logs: github.com/dimagi/django-cte/actions/runs/40487666280/attempts/1

Artifact

Subject: django_cte-4.0.0.dev20261027102036-py3-none-any.whl
SHA-256 checksum: 0da71dc1d53f5bc319e1a0460b9fab255fc7cb8303020b2c81f26093cdd6f310 Verifying attestations

Security for django-cte 4.0.0.dev20261027102036

Report project as malware

Provenance

Full provenance

Both files in this release have been uploaded with provenance metadata.

Attestation for django_cte-4.0.0.dev20261027102036.tar.gz

Identity

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

Workflow

Publishing configuration: github.com/dimagi/django-cte/blob/7afdb68f9db99da8e37d39940f28c244010061c8/.github/workflows/pypi.yml
Publishing logs: github.com/dimagi/django-cte/actions/runs/40487666280/attempts/1

Artifact

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

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.