dirsql 0.4.21__tar.gz → 0.4.22__tar.gz

{dirsql-0.4.21 → dirsql-0.4.22}/Cargo.lock

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

{dirsql-0.4.21 → dirsql-0.4.22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.21
+Version: 0.4.22
 Requires-Dist: tomli>=2 ; python_full_version < '3.11'
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory

{dirsql-0.4.21 → dirsql-0.4.22}/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.21"
+version = "0.4.22"
 # 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.22/packages/python/testing-conventions.toml

@@ -0,0 +1,15 @@
+# Per-package config so `[e2e]` can be per-package: it is one global table
+# applied to every caller reading a given config, so "the core plus MY binding"
+# has nowhere else to live. Folded back into the root file, a napi change would
+# start staling this package.
+#
+# The PyO3 glue is in scope because the console script runs the CLI in-process
+# through it (#721), so every e2e case crosses it. packages/ts/napi is not: it
+# cannot reach this suite.
+[e2e]
+extra_scope = ["packages/rust/src", "packages/python/src"]
+
+# Same floor as the root file, which this lane no longer reads.
+[python.coverage]
+fail_under = 100
+branch = true