turingdb

library1.34.0pypypi✓ verified 84d ago

TuringDB is a graph database engine with support for Cypher-like queries, vector search, and LOAD CSV. Current version is 1.29.0, requiring Python >=3.10. Releases occur roughly monthly, with active development focused on performance, correctness, and new features like SET queries and vector database integration.

database vector-search data

pip install turingdb

github ↗package ↗

INSTALL

IMPORT

SIG · TURINGDB

turingdb

databasepythonv1.34.0

Install

17.9s avg

Import

960ms

Disk

398MB

Pass rate

4/ 10

Env Coverage4 / 10

glibc

3.9–3.13

musl

3.9–3.13

Install & Compatibility

Where this runs

tested against v1.34.0 · pip install

no network on importno background threads

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

glibc

py 3.10

✕ build_error

✓ 22.8s

py 3.11

✕ build_error

✓ 18s

py 3.12

✕ build_error

✓ 15.9s

py 3.13

✕ build_error

✓ 14.9s

py 3.9

✕ build_error

398MB installed

● package 398MB

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

TuringDB

✓ from turingdb import TuringDB

✗ import turingdb.TuringDB

TuringDB is a class, not a submodule. Direct import of the class is correct.

Initialize a local TuringDB instance and run a simple match query.

from turingdb import TuringDB import os db = TuringDB() db.init() result = db.execute("MATCH (n) RETURN n LIMIT 1") print(result) db.close()

Debug

Known issues

breakingIn v1.0 and earlier, the main class was `TuringGraph`. Renamed to `TuringDB` in v1.1. Code using `TuringGraph` will break.

fix

Replace `from turingdb import TuringGraph` with `from turingdb import TuringDB` and update all references.

affects: <1.1

gotcha`TuringDB.init()` must be called before any queries. Failing to do so results in a segmentation fault or undefined behavior.

fix

Always call `db.init()` immediately after creating the `TuringDB` instance.

affects: All

gotchaThe `execute()` method returns results as a pandas DataFrame if pandas is installed, otherwise as a list of dicts. Code relying on one format may break if the other is returned.

fix

Check the type of the result or explicitly convert using `list(result)` for consistent behavior.

affects: All

Errors

Common errors & fixes

AttributeError: module 'turingdb' has no attribute 'TuringDB'

Importing the module incorrectly (e.g., `import turingdb` then `turingdb.TuringDB`) when the correct form is `from turingdb import TuringDB`.

fix

Use: `from turingdb import TuringDB`

Segmentation fault (core dumped)

Calling `execute()` before calling `init()` on the TuringDB instance.

fix

Add `db.init()` immediately after `db = TuringDB()` before any query execution.

turingdb.exceptions.TuringException: Database is not initialized

Attempting to run a query without initializing the database engine.

fix

Ensure `db.init()` is called before any `execute()` call.

Upgrade

Version history

1.34.0latest on PyPI · released Jun 16, 2026

Audit

Dependencies

No dependency data recorded yet.

Agent activity

58 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/turing-db/turingdb ↗

packagehttps://pypi.org/project/turingdb/ ↗