dirsql 0.4.125__tar.gz → 0.4.126__tar.gz

{dirsql-0.4.125 → dirsql-0.4.126}/Cargo.lock

@@ -573,7 +573,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql"
-version = "0.4.125"
+version = "0.4.126"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -625,7 +625,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.125"
+version = "0.4.126"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.125 → dirsql-0.4.126}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.125
+Version: 0.4.126
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index

{dirsql-0.4.125/packages/rust → dirsql-0.4.126}/docs/reference/sdk.md

@@ -300,11 +300,10 @@ Returns a stream of [`RowEvent`](#rowevent)s reflecting filesystem changes
 under the root. The stream never terminates on its own; stop consuming it
 to stop.
 
-A file written once the watcher is live produces an event and reaches the
-index. Rust: the watcher is live when `watch()` returns. Python: it is live
-once both `watch()` and `ready()` have returned, in either order; a write made
-while the initial scan is still running may be missed. TypeScript: the watcher
-starts on first iteration.
+The watcher is live once both `watch()` and [`ready`](#ready) have returned,
+in either order (a Rust `DirSQL` is ready when `build()` returns); a file
+written after that point produces an event and reaches the index. A write
+made while the initial scan is still running may be missed.
 
 An instance with no named tables cannot be watched: path-tables emit no
 watch events, so `watch()` (and the polling primitives) raise an error naming

{dirsql-0.4.125 → dirsql-0.4.126}/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.4.125"
+version = "0.4.126"
 # abi3 note: the `abi3-py310` pyo3 feature (below) builds ONE stable-ABI
 # `cp310-abi3` wheel per platform that loads on every CPython >= 3.10
 # (matching `pyproject.toml`'s `requires-python = ">=3.10"`), instead of

{dirsql-0.4.125 → dirsql-0.4.126/packages/python}/docs/reference/sdk.md

@@ -300,11 +300,10 @@ Returns a stream of [`RowEvent`](#rowevent)s reflecting filesystem changes
 under the root. The stream never terminates on its own; stop consuming it
 to stop.
 
-A file written once the watcher is live produces an event and reaches the
-index. Rust: the watcher is live when `watch()` returns. Python: it is live
-once both `watch()` and `ready()` have returned, in either order; a write made
-while the initial scan is still running may be missed. TypeScript: the watcher
-starts on first iteration.
+The watcher is live once both `watch()` and [`ready`](#ready) have returned,
+in either order (a Rust `DirSQL` is ready when `build()` returns); a file
+written after that point produces an event and reaches the index. A write
+made while the initial scan is still running may be missed.
 
 An instance with no named tables cannot be watched: path-tables emit no
 watch events, so `watch()` (and the polling primitives) raise an error naming

{dirsql-0.4.125 → dirsql-0.4.126}/packages/rust/Cargo.toml

@@ -6,7 +6,7 @@ description = "Ephemeral SQL index over a local directory"
 # version stays for the binding crates (publish = false). The literal
 # intentionally lags the published version: putitoutthere rewrites it to
 # the planned release version at build time and never commits it back.
-version = "0.4.125"
+version = "0.4.126"
 edition.workspace = true
 # Literal `license` (not `license.workspace = true`) because
 # putitoutthere's preflight check reads `[package].license` directly

{dirsql-0.4.125/packages/python → dirsql-0.4.126/packages/rust}/docs/reference/sdk.md

@@ -300,11 +300,10 @@ Returns a stream of [`RowEvent`](#rowevent)s reflecting filesystem changes
 under the root. The stream never terminates on its own; stop consuming it
 to stop.
 
-A file written once the watcher is live produces an event and reaches the
-index. Rust: the watcher is live when `watch()` returns. Python: it is live
-once both `watch()` and `ready()` have returned, in either order; a write made
-while the initial scan is still running may be missed. TypeScript: the watcher
-starts on first iteration.
+The watcher is live once both `watch()` and [`ready`](#ready) have returned,
+in either order (a Rust `DirSQL` is ready when `build()` returns); a file
+written after that point produces an event and reaches the index. A write
+made while the initial scan is still running may be missed.
 
 An instance with no named tables cannot be watched: path-tables emit no
 watch events, so `watch()` (and the polling primitives) raise an error naming