dj-turso
A Django database backend for Turso, the Rust rewrite of SQLite. Use a local database file in development and Turso Cloud in production, with one engine.
Status: alpha. Requires Django 6.1 and Python 3.12+.
Install
pip install dj-turso
Use a local file
DATABASES = {
"default": {
"ENGINE": "dj_turso",
"NAME": "default.db",
},
}
Use Turso Cloud
pip install "dj-turso[serverless]"
DATABASES = {
"default": {
"ENGINE": "dj_turso",
"NAME": "turso://my-database.turso.io",
"OPTIONS": {"auth_token": os.environ["TURSO_AUTH_TOKEN"]},
},
}
Good to know
- A local file opens in one process at a time: fine for
runserverand tests, not for a server with several workers. Use Turso Cloud there. - A Turso Cloud database must be on the Turso engine, not libSQL.
- Date lookups need the active time zone to match the database's, UTC by default.
Learn more
- Testing your project
- Compatibility: regular expressions, unsupported features, known Turso bugs
- Example project
- Contributing
- Changelog
Metadata
Release files for dj-turso 0.1.0
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 |
|---|---|---|---|---|
| dj_turso-0.1.0.tar.gz | 22.9 kB | With provenance | Details for dj_turso-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dj_turso-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dj_turso-0.1.0-py3-none-any.whl |
Total release size: 48.8 kB
Release files / dj_turso-0.1.0.tar.gz
| Download URL | dj_turso-0.1.0.tar.gz |
|---|---|
| Size | 22.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d63596615ba704bc0cb665f202ae492af095d16f5aff8e3594a256d1f572187
|
|
BLAKE2b-256 checksum How to use checksums |
863377484b7692c2456a5a6dc036ea47a9812750327d440f4faa1737b84f56f2
|
| 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 Nov 21, 2026.
Transparency logRelease files / dj_turso-0.1.0-py3-none-any.whl
| Download URL | dj_turso-0.1.0-py3-none-any.whl |
|---|---|
| Size | 25.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd94ee53327ef470653843082e21f0ab1a066790282843aacdee6c1fc1ae6df2
|
|
BLAKE2b-256 checksum How to use checksums |
5b5f9806b0dfce119c0b32fbd320d61219ca40769c96d0b77b8e51176b6166b2
|
| 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 Nov 21, 2026.
Transparency logSecurity for dj-turso 0.1.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for dj_turso-0.1.0.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 Nov 21, 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.