dirsql 0.3.41__tar.gz → 0.3.43__tar.gz

{dirsql-0.3.41 → dirsql-0.3.43}/Cargo.lock

@@ -499,7 +499,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.3.41"
+version = "0.3.43"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.3.41 → dirsql-0.3.43}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.3.41
+Version: 0.3.43
 Requires-Dist: pytest>=8 ; extra == 'dev'
 Requires-Dist: pytest-describe>=2 ; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23 ; extra == 'dev'

{dirsql-0.3.41 → dirsql-0.3.43}/dirsql/_async.py

@@ -1,20 +1,8 @@
 """Async-by-default DirSQL wrapper."""
 
 import asyncio
-from typing import TYPE_CHECKING
 
 from dirsql._dirsql import DirSQL as _RustDirSQL
-from dirsql.resolve_config import resolve_config
-
-if TYPE_CHECKING:
-    # `typing.override` is 3.12+; the package supports 3.11, so source it from
-    # `typing_extensions` for the type checker only. At runtime `@override` is
-    # a pure marker, so a no-op identity avoids the runtime dependency.
-    from typing_extensions import override
-else:
-
-    def override(func):
-        return func
 
 
 class _WatchStream:
@@ -135,21 +123,3 @@ class DirSQL:
     def watch(self):
         """Start watching for file changes. Returns an async iterable of RowEvent."""
         return _WatchStream(self._db)
-
-    @property
-    @override
-    def __dict__(self):
-        """Resolved construction state as a JSON-serializable dict.
-
-        Recomputed on each access; reads the ``.dirsql.toml`` if ``config=``
-        was supplied. Works before ``await db.ready()``.
-        """
-        return resolve_config(
-            self._root,
-            self._tables,
-            self._ignore,
-            self._config,
-            self._persist,
-            self._persist_path,
-            self._extensions,
-        )

dirsql-0.3.43/dirsql/cli/interpret/__init__.py

@@ -0,0 +1,14 @@
+"""Empty package shell — the native-config ``interpret`` helper was removed.
+
+The ``dirsql interpret`` subcommand and its NDJSON ``extract`` loop (``run``,
+``load_app``, ``dispatch_extract``, ``write_message``) were removed in #321
+(#323). The CLI now accepts only ``.dirsql.toml``; to run user-defined
+``extract`` callbacks, use the programmatic SDK (``DirSQL(...)`` with
+in-process closures).
+
+This ``__init__.py`` carries no logic and no re-exports. It remains only
+because the colocated-test tooling cannot yet express *deleting* an exempt
+package barrel (the co-change check flags a deleted source that has no
+co-deleted colocated test, and a retained exempt for a deleted path is
+rejected as stale). The directory is removed once that is resolved.
+"""

{dirsql-0.3.41 → dirsql-0.3.43}/dirsql/cli/main.py

@@ -1,8 +1,6 @@
 """Console-script entry point. Execs the bundled binary on POSIX,
-subprocesses it on Windows. When ``argv[0] == "interpret"`` the
-in-process Python helper handles the subcommand directly so a Rust
-orchestrator can spawn this script for native-language configs (#196)
-without depending on the bundled Rust binary."""
+subprocesses it on Windows. All argv is forwarded transparently to the
+bundled Rust binary."""
 
 from __future__ import annotations
 
@@ -18,14 +16,6 @@ def main(argv: list[str] | None = None) -> int:
     if argv is None:
         argv = sys.argv[1:]
 
-    if argv and argv[0] == "interpret":
-        from .interpret.run import run
-
-        try:
-            return run(argv[1:])
-        except KeyboardInterrupt:
-            return 130
-
     try:
         binary = binary_path()
     except FileNotFoundError as exc:

{dirsql-0.3.41/packages/python → dirsql-0.3.43}/docs/AGENTS.md

@@ -45,19 +45,17 @@ The docs follow the [Diataxis](https://diataxis.fr/) framework:
 The **CLI** (`cli/`) is a self-contained section reachable from its own
 top-level `CLI` nav tab, with a path-scoped sidebar (`/cli/` key in
 `config.ts`). Everything a CLI user needs -- installation, running the server,
-`init`, config files (`.dirsql.toml` or native-language), and the HTTP API --
-lives under `cli/`. Do not move CLI pages back into `guide/`.
+`init`, the `.dirsql.toml` config file, and the HTTP API -- lives under
+`cli/`. Do not move CLI pages back into `guide/`.
 
 ## Conventions
 
 - **Lead with the use case.** Open each feature description with *why* a
   reader would reach for it before *how* it works. Don't frame a feature
   by what an adjacent feature can't do.
-  *Don't:* "`.dirsql.toml` can't parse contents — you need code in
-  `extract`. Point `--config` at a Python module..."
-  *Do:* "Native-language configs let you build tables from the
-  *contents* of files — frontmatter, JSON values, CSV cells — by
-  writing a dynamic `extract` callback."
+  *Don't:* "Persistence avoids the thing the default mode can't do..."
+  *Do:* "Persistence keeps the SQLite index on disk between runs so large
+  directories don't re-scan on every startup."
 - Wrap `dirsql` in backticks in all prose text
 - Use VitePress [code group](https://vitepress.dev/guide/markdown#code-groups) syntax (`::: code-group`) for multi-language examples with `Python`, `Rust`, and `TypeScript` tabs
 - Internal links use relative paths (e.g., `./guide/tables.md`)

{dirsql-0.3.41/packages/rust → dirsql-0.3.43}/docs/api/index.md

@@ -59,6 +59,7 @@ new DirSQL({
     tables?: TableDef[],
     ignore?: string[],
     config?: string,
+    extensions?: ExtensionSpec[],  // [{ path: string, entrypoint?: string }]
 })
 ```
 
@@ -76,7 +77,7 @@ In Python, the constructor starts scanning in a background thread and returns im
 - `tables` -- List of `Table` definitions. Each defines a SQLite table, a glob pattern, and an extract function.
 - `ignore` -- Optional list of glob patterns. Files matching any ignore pattern are skipped regardless of table globs.
 - `config` -- Optional path to a `.dirsql.toml` config file. Its `[[table]]` entries are appended to any programmatic `tables`; its `[dirsql].ignore` patterns are appended to any explicit `ignore`; its optional `[dirsql].root` supplies the root directory when `root` is not passed explicitly; its `[[dirsql.extension]]` entries are appended to any programmatic `extensions`.
-- `extensions` -- Optional SQLite extensions to load onto the connection at startup, before any table DDL (enable → load → disable, so the SQL `load_extension()` function is never left exposed). Each entry pairs a shared-library `path` with an optional `entrypoint` init-symbol override (Python: `{ "path", "entrypoint"? }` dicts; Rust: `Extension { path, entrypoint }`). Programmatic entries load first, then any `[[dirsql.extension]]` from `config`. Available in the Python and Rust SDKs; the TypeScript constructor parameter is tracked in [#230](https://github.com/thekevinscott/dirsql/issues/230). See [Loading extensions](../cli/config.md#loading-extensions).
+- `extensions` -- Optional SQLite extensions to load onto the connection at startup, before any table DDL (enable → load → disable, so the SQL `load_extension()` function is never left exposed). Each entry pairs a shared-library `path` with an optional `entrypoint` init-symbol override (Python: `{ "path", "entrypoint"? }` dicts; Rust: `Extension { path, entrypoint }`; TypeScript: `{ path, entrypoint? }` objects). Programmatic entries load first, then any `[[dirsql.extension]]` from `config`. Available in the Python, Rust, and TypeScript SDKs. See [Loading extensions](../cli/config.md#loading-extensions).
 
 ### Methods
 
@@ -144,26 +145,6 @@ for await (const event of db.watch()) {  // AsyncIterable<RowEvent>
 
 Returns an async iterable of `RowEvent` objects. The file watcher starts automatically on first iteration. The iterator never terminates on its own.
 
-#### `serialization`
-
-::: code-group
-
-```python [Python]
-vars(db) -> dict
-```
-
-```rust [Rust]
-db.config() -> DirSQLConfig
-```
-
-```typescript [TypeScript]
-JSON.stringify(db)  // via db.toJSON()
-```
-
-:::
-
-Returns the resolved construction state as a JSON-compatible value with fields `root`, `tables`, `ignore`, `persist`, `persist_path` (camelCase `persistPath` in TypeScript). Each table is `{ ddl, glob, strict }`. The Python and Rust snapshots also include `extensions` -- an array of `{ path, entrypoint }` (empty when none are configured); the TypeScript `toJSON` snapshot will gain it with [#230](https://github.com/thekevinscott/dirsql/issues/230). Excludes the original `config` path (already merged into `root` / `tables` / `ignore`), per-table `extract`, and per-table `name`. Available immediately after construction in Python and TypeScript; Rust's sync `build()` returns a ready instance.
-
 ---
 
 ## Table
@@ -212,7 +193,7 @@ Defines a mapping from files to SQLite table rows.
 - `ddl` -- A `CREATE TABLE` statement. The table name is parsed from this DDL.
 - `glob` -- A glob pattern matched against file paths relative to the root directory.
 - `extract` -- A callable `(path) -> list[dict]`. Receives the path of the matched file -- relative to the scan root, or absolute when `root` is absolute. `dirsql` does not read file contents; a callback that needs the file body reads `path` itself. Returns a list of dicts/maps mapping column names to values. Return an empty list to skip a file.
-- `strict` -- Optional (default `False`). Controls row/schema validation. In the default relaxed mode, extra row keys are dropped and missing columns become `NULL`. When `True`, every row key must be a valid column identifier and any extra or missing key raises an error. Surfaced in [serialization](#serialization) above as part of each table's `{ ddl, glob, strict }`.
+- `strict` -- Optional (default `False`). Controls row/schema validation. In the default relaxed mode, extra row keys are dropped and missing columns become `NULL`. When `True`, every row key must be a valid column identifier and any extra or missing key raises an error.
 
 **Attributes:**
 

{dirsql-0.3.41 → dirsql-0.3.43}/docs/cli/config.md

@@ -6,16 +6,10 @@ canonical: https://thekevinscott.github.io/dirsql/cli/config
 
 > Online: <https://thekevinscott.github.io/dirsql/cli/config>
 
-`dirsql` is configured with an optional config file; with none, the server
-falls back to [zero-config defaults](./server.md#defaults). Choose a format by
-what you need:
-
-- **[TOML](#toml)** — declarative; defines filesystem-fact tables (the path,
-  glob captures, and stat metadata). Works with any installation.
-- **[Python](#python)** and **[JavaScript](#javascript)** — native-language
-  configs that build tables from the *contents* of files (frontmatter, JSON
-  values, CSV cells) through a dynamic `extract` callback. CLI-only; only the
-  launcher matching the file's language can run it.
+`dirsql` is configured with an optional `.dirsql.toml` file; with none, the
+server falls back to [zero-config defaults](./server.md#defaults). A
+[TOML](#toml) config is declarative: it defines filesystem-fact tables (the
+path, glob captures, and stat metadata) and works with any installation.
 
 ## TOML
 
@@ -194,9 +188,8 @@ strict = true
 
 Strict mode does **not** apply to auto-injected stat virtuals — those are
 always filtered to the DDL's declared columns regardless. Strict mode
-applies only to keys produced by an extract callback (relevant for the
-[Python](#python) / [JavaScript](#javascript) configs below and programmatic
-[tables](../guide/tables.md)).
+applies only to keys produced by an extract callback (relevant for
+programmatic [tables](../guide/tables.md)).
 
 ### Full Example
 
@@ -216,108 +209,3 @@ glob = "**/index.md"
 ddl  = "CREATE TABLE logs (_path TEXT, _size INTEGER, _mtime INTEGER)"
 glob = "logs/*.csv"
 ```
-
-## Python
-
-Reach for a Python config when your columns come from the *contents* of a
-file — parsed JSON, frontmatter, CSV cells — rather than from filesystem
-facts alone. You write a dynamic `extract` callback in Python, and the file
-otherwise looks exactly like the in-process SDK construction (same `DirSQL` /
-`Table` API):
-
-```bash
-dirsql --config dirsql.config.py
-```
-
-```python [dirsql.config.py]
-import json
-from dirsql import DirSQL, Table
-
-def extract_meta(path):
-    with open(path) as f:
-        return [json.load(f)]
-
-# Python must export a module-level `app`.
-app = DirSQL(
-    root="papers",  # optional; defaults to the current directory
-    tables=[
-        Table(
-            ddl="CREATE TABLE papers (title TEXT, _path TEXT)",
-            glob="**/meta.json",
-            extract=extract_meta,
-        ),
-    ],
-)
-```
-
-`extract` receives the path of each matched file and returns a list of rows
-(one dict per row).
-
-## JavaScript
-
-A JavaScript config gives you the same contents-driven `extract` in Node,
-in either ES module or CommonJS form:
-
-```bash
-dirsql --config dirsql.config.mjs
-```
-
-::: code-group
-
-```javascript [dirsql.config.mjs]
-import { readFileSync } from "node:fs";
-import { DirSQL } from "dirsql";
-
-export default new DirSQL({
-  root: "papers", // optional; defaults to the current directory
-  tables: [
-    {
-      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
-      glob: "**/meta.json",
-      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
-    },
-  ],
-});
-```
-
-```javascript [dirsql.config.cjs]
-const { readFileSync } = require("node:fs");
-const { DirSQL } = require("dirsql");
-
-module.exports = new DirSQL({
-  root: "papers", // optional; defaults to the current directory
-  tables: [
-    {
-      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
-      glob: "**/meta.json",
-      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
-    },
-  ],
-});
-```
-
-:::
-
-## Notes for native-language configs
-
-These apply to both the Python and JavaScript forms above.
-
-- **Export the config.** Python exposes a module-level `app = DirSQL(...)`; an
-  ES module (`.mjs`, or `.js` in an ESM package) uses
-  `export default new DirSQL(...)`; CommonJS (`.cjs`, or `.js` in a CJS
-  package) uses `module.exports = new DirSQL(...)`. Only the extension
-  matters — the file can be named anything; `dirsql.config.{py,mjs,cjs}` is the
-  suggested convention, not a requirement.
-- **`root` defaults to the current directory.** A native-language config with
-  no `root` indexes the process's current working directory — the directory you
-  ran `dirsql` from. (This differs from TOML configs, which default the scan
-  root to the config file's own directory.) Pass `root` explicitly to index
-  somewhere else.
-- **No nested `config=`.** A native-language config builds its `DirSQL` from
-  `tables` and an optional `root`; it must not itself set `config=` to delegate
-  to another config file. `dirsql interpret` rejects such a config (a nested
-  config can't be represented in the handshake and would recurse).
-- **Install the launcher on your `PATH`.** To run your `extract`, the server
-  spawns `dirsql interpret`, so the matching `dirsql` launcher must be installed
-  and on your `PATH` — a global `pip`/`uv` install for `.py`, or `npm` for
-  `.mjs` / `.cjs`. Only the launcher matching the file's language can run it.

{dirsql-0.3.41/packages/rust → dirsql-0.3.43}/docs/cli/index.md

@@ -17,9 +17,8 @@ Everything you need to run `dirsql` as a CLI lives in this section:
 - **[Installation](#installation)** — get the `dirsql` binary.
 - **[Running the Server](./server.md)** — subcommands and flags.
 - **[Generating a Config (`init`)](./init.md)** — scaffold a `.dirsql.toml`.
-- **[Configuration File](./config.md)** — the `.dirsql.toml` format and the
-  `.py` / `.js` native-language alternative. Custom tables
-  are defined through a config file; without one, the server runs in
+- **[Configuration File](./config.md)** — the `.dirsql.toml` format. Custom
+  tables are defined through a config file; without one, the server runs in
   [zero-config mode](./server.md#defaults).
 - **[HTTP API](./http-api.md)** — the `POST /query` and `GET /events`
   endpoints, status codes, and event streaming.

{dirsql-0.3.41/packages/rust → dirsql-0.3.43}/docs/cli/server.md

@@ -28,8 +28,7 @@ $ Running at localhost:7117
 
 The server reads tables from a [config file](./config.md). By default it
 looks for `./.dirsql.toml`; pass `--config <path>` to point at a different
-`.toml` file or a [native-language config](./config.md)
-(`.py` / `.js`).
+`.toml` file.
 
 ## Defaults
 
@@ -53,7 +52,7 @@ A config file will override the default.
 
 | Flag | Default | Description |
 |---|---|---|
-| `--config <path>` | `./.dirsql.toml` | Path to the config file (`.toml` or [native-language](./config.md)). The index is rooted at the directory containing this file. |
+| `--config <path>` | `./.dirsql.toml` | Path to the `.toml` [config file](./config.md). The index is rooted at the directory containing this file. |
 | `--host <addr>` | `localhost` | Bind address |
 | `--port <n>` | `7117` | TCP port to bind |
 

{dirsql-0.3.41 → dirsql-0.3.43}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.3.41"
+version = "0.3.43"
 edition.workspace = true
 publish = false
 readme = "README.md"

{dirsql-0.3.41 → dirsql-0.3.43/packages/python}/docs/AGENTS.md

@@ -45,19 +45,17 @@ The docs follow the [Diataxis](https://diataxis.fr/) framework:
 The **CLI** (`cli/`) is a self-contained section reachable from its own
 top-level `CLI` nav tab, with a path-scoped sidebar (`/cli/` key in
 `config.ts`). Everything a CLI user needs -- installation, running the server,
-`init`, config files (`.dirsql.toml` or native-language), and the HTTP API --
-lives under `cli/`. Do not move CLI pages back into `guide/`.
+`init`, the `.dirsql.toml` config file, and the HTTP API -- lives under
+`cli/`. Do not move CLI pages back into `guide/`.
 
 ## Conventions
 
 - **Lead with the use case.** Open each feature description with *why* a
   reader would reach for it before *how* it works. Don't frame a feature
   by what an adjacent feature can't do.
-  *Don't:* "`.dirsql.toml` can't parse contents — you need code in
-  `extract`. Point `--config` at a Python module..."
-  *Do:* "Native-language configs let you build tables from the
-  *contents* of files — frontmatter, JSON values, CSV cells — by
-  writing a dynamic `extract` callback."
+  *Don't:* "Persistence avoids the thing the default mode can't do..."
+  *Do:* "Persistence keeps the SQLite index on disk between runs so large
+  directories don't re-scan on every startup."
 - Wrap `dirsql` in backticks in all prose text
 - Use VitePress [code group](https://vitepress.dev/guide/markdown#code-groups) syntax (`::: code-group`) for multi-language examples with `Python`, `Rust`, and `TypeScript` tabs
 - Internal links use relative paths (e.g., `./guide/tables.md`)

{dirsql-0.3.41 → dirsql-0.3.43/packages/python}/docs/api/index.md

@@ -59,6 +59,7 @@ new DirSQL({
     tables?: TableDef[],
     ignore?: string[],
     config?: string,
+    extensions?: ExtensionSpec[],  // [{ path: string, entrypoint?: string }]
 })
 ```
 
@@ -76,7 +77,7 @@ In Python, the constructor starts scanning in a background thread and returns im
 - `tables` -- List of `Table` definitions. Each defines a SQLite table, a glob pattern, and an extract function.
 - `ignore` -- Optional list of glob patterns. Files matching any ignore pattern are skipped regardless of table globs.
 - `config` -- Optional path to a `.dirsql.toml` config file. Its `[[table]]` entries are appended to any programmatic `tables`; its `[dirsql].ignore` patterns are appended to any explicit `ignore`; its optional `[dirsql].root` supplies the root directory when `root` is not passed explicitly; its `[[dirsql.extension]]` entries are appended to any programmatic `extensions`.
-- `extensions` -- Optional SQLite extensions to load onto the connection at startup, before any table DDL (enable → load → disable, so the SQL `load_extension()` function is never left exposed). Each entry pairs a shared-library `path` with an optional `entrypoint` init-symbol override (Python: `{ "path", "entrypoint"? }` dicts; Rust: `Extension { path, entrypoint }`). Programmatic entries load first, then any `[[dirsql.extension]]` from `config`. Available in the Python and Rust SDKs; the TypeScript constructor parameter is tracked in [#230](https://github.com/thekevinscott/dirsql/issues/230). See [Loading extensions](../cli/config.md#loading-extensions).
+- `extensions` -- Optional SQLite extensions to load onto the connection at startup, before any table DDL (enable → load → disable, so the SQL `load_extension()` function is never left exposed). Each entry pairs a shared-library `path` with an optional `entrypoint` init-symbol override (Python: `{ "path", "entrypoint"? }` dicts; Rust: `Extension { path, entrypoint }`; TypeScript: `{ path, entrypoint? }` objects). Programmatic entries load first, then any `[[dirsql.extension]]` from `config`. Available in the Python, Rust, and TypeScript SDKs. See [Loading extensions](../cli/config.md#loading-extensions).
 
 ### Methods
 
@@ -144,26 +145,6 @@ for await (const event of db.watch()) {  // AsyncIterable<RowEvent>
 
 Returns an async iterable of `RowEvent` objects. The file watcher starts automatically on first iteration. The iterator never terminates on its own.
 
-#### `serialization`
-
-::: code-group
-
-```python [Python]
-vars(db) -> dict
-```
-
-```rust [Rust]
-db.config() -> DirSQLConfig
-```
-
-```typescript [TypeScript]
-JSON.stringify(db)  // via db.toJSON()
-```
-
-:::
-
-Returns the resolved construction state as a JSON-compatible value with fields `root`, `tables`, `ignore`, `persist`, `persist_path` (camelCase `persistPath` in TypeScript). Each table is `{ ddl, glob, strict }`. The Python and Rust snapshots also include `extensions` -- an array of `{ path, entrypoint }` (empty when none are configured); the TypeScript `toJSON` snapshot will gain it with [#230](https://github.com/thekevinscott/dirsql/issues/230). Excludes the original `config` path (already merged into `root` / `tables` / `ignore`), per-table `extract`, and per-table `name`. Available immediately after construction in Python and TypeScript; Rust's sync `build()` returns a ready instance.
-
 ---
 
 ## Table
@@ -212,7 +193,7 @@ Defines a mapping from files to SQLite table rows.
 - `ddl` -- A `CREATE TABLE` statement. The table name is parsed from this DDL.
 - `glob` -- A glob pattern matched against file paths relative to the root directory.
 - `extract` -- A callable `(path) -> list[dict]`. Receives the path of the matched file -- relative to the scan root, or absolute when `root` is absolute. `dirsql` does not read file contents; a callback that needs the file body reads `path` itself. Returns a list of dicts/maps mapping column names to values. Return an empty list to skip a file.
-- `strict` -- Optional (default `False`). Controls row/schema validation. In the default relaxed mode, extra row keys are dropped and missing columns become `NULL`. When `True`, every row key must be a valid column identifier and any extra or missing key raises an error. Surfaced in [serialization](#serialization) above as part of each table's `{ ddl, glob, strict }`.
+- `strict` -- Optional (default `False`). Controls row/schema validation. In the default relaxed mode, extra row keys are dropped and missing columns become `NULL`. When `True`, every row key must be a valid column identifier and any extra or missing key raises an error.
 
 **Attributes:**
 

{dirsql-0.3.41 → dirsql-0.3.43}/packages/python/docs/cli/config.md

@@ -6,16 +6,10 @@ canonical: https://thekevinscott.github.io/dirsql/cli/config
 
 > Online: <https://thekevinscott.github.io/dirsql/cli/config>
 
-`dirsql` is configured with an optional config file; with none, the server
-falls back to [zero-config defaults](./server.md#defaults). Choose a format by
-what you need:
-
-- **[TOML](#toml)** — declarative; defines filesystem-fact tables (the path,
-  glob captures, and stat metadata). Works with any installation.
-- **[Python](#python)** and **[JavaScript](#javascript)** — native-language
-  configs that build tables from the *contents* of files (frontmatter, JSON
-  values, CSV cells) through a dynamic `extract` callback. CLI-only; only the
-  launcher matching the file's language can run it.
+`dirsql` is configured with an optional `.dirsql.toml` file; with none, the
+server falls back to [zero-config defaults](./server.md#defaults). A
+[TOML](#toml) config is declarative: it defines filesystem-fact tables (the
+path, glob captures, and stat metadata) and works with any installation.
 
 ## TOML
 
@@ -194,9 +188,8 @@ strict = true
 
 Strict mode does **not** apply to auto-injected stat virtuals — those are
 always filtered to the DDL's declared columns regardless. Strict mode
-applies only to keys produced by an extract callback (relevant for the
-[Python](#python) / [JavaScript](#javascript) configs below and programmatic
-[tables](../guide/tables.md)).
+applies only to keys produced by an extract callback (relevant for
+programmatic [tables](../guide/tables.md)).
 
 ### Full Example
 
@@ -216,108 +209,3 @@ glob = "**/index.md"
 ddl  = "CREATE TABLE logs (_path TEXT, _size INTEGER, _mtime INTEGER)"
 glob = "logs/*.csv"
 ```
-
-## Python
-
-Reach for a Python config when your columns come from the *contents* of a
-file — parsed JSON, frontmatter, CSV cells — rather than from filesystem
-facts alone. You write a dynamic `extract` callback in Python, and the file
-otherwise looks exactly like the in-process SDK construction (same `DirSQL` /
-`Table` API):
-
-```bash
-dirsql --config dirsql.config.py
-```
-
-```python [dirsql.config.py]
-import json
-from dirsql import DirSQL, Table
-
-def extract_meta(path):
-    with open(path) as f:
-        return [json.load(f)]
-
-# Python must export a module-level `app`.
-app = DirSQL(
-    root="papers",  # optional; defaults to the current directory
-    tables=[
-        Table(
-            ddl="CREATE TABLE papers (title TEXT, _path TEXT)",
-            glob="**/meta.json",
-            extract=extract_meta,
-        ),
-    ],
-)
-```
-
-`extract` receives the path of each matched file and returns a list of rows
-(one dict per row).
-
-## JavaScript
-
-A JavaScript config gives you the same contents-driven `extract` in Node,
-in either ES module or CommonJS form:
-
-```bash
-dirsql --config dirsql.config.mjs
-```
-
-::: code-group
-
-```javascript [dirsql.config.mjs]
-import { readFileSync } from "node:fs";
-import { DirSQL } from "dirsql";
-
-export default new DirSQL({
-  root: "papers", // optional; defaults to the current directory
-  tables: [
-    {
-      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
-      glob: "**/meta.json",
-      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
-    },
-  ],
-});
-```
-
-```javascript [dirsql.config.cjs]
-const { readFileSync } = require("node:fs");
-const { DirSQL } = require("dirsql");
-
-module.exports = new DirSQL({
-  root: "papers", // optional; defaults to the current directory
-  tables: [
-    {
-      ddl: "CREATE TABLE papers (title TEXT, _path TEXT)",
-      glob: "**/meta.json",
-      extract: (path) => [JSON.parse(readFileSync(path, "utf8"))],
-    },
-  ],
-});
-```
-
-:::
-
-## Notes for native-language configs
-
-These apply to both the Python and JavaScript forms above.
-
-- **Export the config.** Python exposes a module-level `app = DirSQL(...)`; an
-  ES module (`.mjs`, or `.js` in an ESM package) uses
-  `export default new DirSQL(...)`; CommonJS (`.cjs`, or `.js` in a CJS
-  package) uses `module.exports = new DirSQL(...)`. Only the extension
-  matters — the file can be named anything; `dirsql.config.{py,mjs,cjs}` is the
-  suggested convention, not a requirement.
-- **`root` defaults to the current directory.** A native-language config with
-  no `root` indexes the process's current working directory — the directory you
-  ran `dirsql` from. (This differs from TOML configs, which default the scan
-  root to the config file's own directory.) Pass `root` explicitly to index
-  somewhere else.
-- **No nested `config=`.** A native-language config builds its `DirSQL` from
-  `tables` and an optional `root`; it must not itself set `config=` to delegate
-  to another config file. `dirsql interpret` rejects such a config (a nested
-  config can't be represented in the handshake and would recurse).
-- **Install the launcher on your `PATH`.** To run your `extract`, the server
-  spawns `dirsql interpret`, so the matching `dirsql` launcher must be installed
-  and on your `PATH` — a global `pip`/`uv` install for `.py`, or `npm` for
-  `.mjs` / `.cjs`. Only the launcher matching the file's language can run it.

{dirsql-0.3.41 → dirsql-0.3.43/packages/python}/docs/cli/index.md

@@ -17,9 +17,8 @@ Everything you need to run `dirsql` as a CLI lives in this section:
 - **[Installation](#installation)** — get the `dirsql` binary.
 - **[Running the Server](./server.md)** — subcommands and flags.
 - **[Generating a Config (`init`)](./init.md)** — scaffold a `.dirsql.toml`.
-- **[Configuration File](./config.md)** — the `.dirsql.toml` format and the
-  `.py` / `.js` native-language alternative. Custom tables
-  are defined through a config file; without one, the server runs in
+- **[Configuration File](./config.md)** — the `.dirsql.toml` format. Custom
+  tables are defined through a config file; without one, the server runs in
   [zero-config mode](./server.md#defaults).
 - **[HTTP API](./http-api.md)** — the `POST /query` and `GET /events`
   endpoints, status codes, and event streaming.

{dirsql-0.3.41 → dirsql-0.3.43}/packages/python/docs/cli/server.md

@@ -28,8 +28,7 @@ $ Running at localhost:7117
 
 The server reads tables from a [config file](./config.md). By default it
 looks for `./.dirsql.toml`; pass `--config <path>` to point at a different
-`.toml` file or a [native-language config](./config.md)
-(`.py` / `.js`).
+`.toml` file.
 
 ## Defaults
 
@@ -53,7 +52,7 @@ A config file will override the default.
 
 | Flag | Default | Description |
 |---|---|---|
-| `--config <path>` | `./.dirsql.toml` | Path to the config file (`.toml` or [native-language](./config.md)). The index is rooted at the directory containing this file. |
+| `--config <path>` | `./.dirsql.toml` | Path to the `.toml` [config file](./config.md). The index is rooted at the directory containing this file. |
 | `--host <addr>` | `localhost` | Bind address |
 | `--port <n>` | `7117` | TCP port to bind |
 

{dirsql-0.3.41 → dirsql-0.3.43}/packages/python/e2e-attestation.json

@@ -1,6 +1,6 @@
 {
   "command": "uv run python -m pytest tests/e2e/ -x -q",
-  "ran_at": 1782763249,
+  "ran_at": 1782833107,
   "exit_code": 0,
-  "commit": "8a3051871b21e04c0c2c2cc11a57e4c0a9b94866"
+  "commit": "07bd37825c22f9ad73153d70fc65c9e3c92f855e"
 }