supercov 0.0.29 → 0.0.31

package/README.md

@@ -38,6 +38,8 @@ npx supercov -- npx playwright test
 npx supercov -- pnpm test:e2e
 npx supercov -- cargo test
 npx supercov -- cargo nextest run
+npx supercov -- pytest
+npx supercov -- python -m unittest
 ```
 
 ## Give Supercov a job
@@ -106,12 +108,12 @@ The denominator comes from source structure before the run, so adding or removin
 | JavaScript | Available | `npx supercov -- npm test` |
 | TypeScript | Available | `npx supercov -- npm test` |
 | Rust | Available | `npx supercov -- cargo test` |
-| Python | Coming soon | — |
+| Python | Available | `npx supercov -- pytest` |
 | Zig | Coming soon | — |
 | PHP | Coming soon | — |
 | C | Coming soon | — |
 
-Supercov requires Node.js 22 or newer. Rust support currently uses Rust 1.95; cargo-nextest 0.9.138 and 0.9.140 are supported.
+Supercov requires Node.js 22 or newer. Rust support currently uses Rust 1.95; cargo-nextest 0.9.138 and 0.9.140 are supported. Python support requires CPython 3.12 or newer and measures pytest and unittest runs.
 
 ## Supported test suites
 

package/docs/getting-started.md

@@ -9,7 +9,7 @@ npx supercov -- npm test
 ```
 
 No account, config file, import, custom reporter, or hosted service is required.
-Supercov supports JavaScript, TypeScript, and Rust today.
+Supercov supports JavaScript, TypeScript, Rust, and Python today.
 
 ## Before you start
 
@@ -17,7 +17,8 @@ You need:
 
 - Node.js 22 or newer;
 - a test command that already works in the repository; and
-- for Rust, the Rust 1.95 toolchain.
+- for Rust, the Rust 1.95 toolchain;
+- for Python, CPython 3.12 or newer with pytest or unittest.
 
 The CLI is distributed through npm, even for Rust projects. The first `npx`
 invocation may download Supercov from the npm registry. Supercov itself does not
@@ -37,6 +38,9 @@ npx supercov -- pnpm test:e2e
 # Rust
 npx supercov -- cargo test
 npx supercov -- cargo nextest run
+
+# Python
+npx supercov -- pytest
 ```
 
 Supercov runs that command in an isolated, instrumented copy of the project.

package/docs/supported-suites.md

@@ -1,13 +1,14 @@
 # Supported languages and test suites
 
-Supercov supports JavaScript, TypeScript, and Rust today. Start with the same
-test command the repository already uses; Supercov detects supported runners
-inside that command.
+Supercov supports JavaScript, TypeScript, Rust, and Python today. Start with
+the same test command the repository already uses; Supercov detects supported
+runners inside that command.
 
 ```sh
 npx supercov -- npm test
 npx supercov -- npx playwright test
 npx supercov -- cargo test
+npx supercov -- pytest
 ```
 
 ## Language support
@@ -17,7 +18,7 @@ npx supercov -- cargo test
 | JavaScript | Available | `npx supercov -- npm test` |
 | TypeScript | Available | `npx supercov -- npm test` |
 | Rust | Available | `npx supercov -- cargo test` |
-| Python | Coming soon | — |
+| Python | Available | `npx supercov -- pytest` |
 | Zig | Coming soon | — |
 | PHP | Coming soon | — |
 | C | Coming soon | — |
@@ -91,6 +92,43 @@ npx supercov -- cargo nextest run --workspace
 explanation instead of silently falling back to plausible but inaccurate
 attribution.
 
+## Python
+
+| Runner | Attribution | Current requirement |
+| --- | --- | --- |
+| pytest | Exact test, worker, retry, and setup/call/teardown phase identity | CPython 3.12 or newer; run with `npx supercov -- pytest` or `python -m pytest` |
+| pytest-xdist | Exact per worker | Workers inherit the run through the environment |
+| pytest-rerunfailures | Exact per attempt; flaky tests are reported as such | |
+| `python -m unittest` | Exact test and setUp/test/tearDown phase identity | Serial in-process; skips and expected failures are recorded; subtest failures roll up to the parent test |
+
+Supercov measures Python through CPython's own monitoring interface. Nothing is
+copied, rewritten, or compiled differently: the project runs in place with its
+own interpreter and virtual environment, and Supercov only adds a start-up hook
+through `PYTHONPATH`, a pytest plugin through `PYTEST_PLUGINS`, and a few
+`SUPERCOV_*` variables. Child interpreters started with `subprocess` or
+`multiprocessing` inherit the exact test identity; threads and thread pools
+carry it through `contextvars`.
+
+Each interpreter writes commit-framed evidence to a process-owned mmap. A hard
+kill preserves completed observations and an incomplete tail is ignored; an
+exhausted transport or corrupt committed frame fails the run closed.
+
+Measured obligations are statements (including several on one line), function
+entry, boolean decisions with MC/DC vectors, `for` and comprehension iteration,
+`and`/`or` short-circuiting, `match` case selection, and `try` completion,
+handler selection and exception propagation, all derived from CPython's own
+instruction positions rather than from exception hooks.
+
+Interpreters launched with `-I`, `-E`, or `-S` ignore `PYTHONPATH` and are not
+measured. Code compiled from strings at runtime has no source obligations.
+
+```sh
+npx supercov -- pytest
+npx supercov -- python -m pytest -n 4
+npx supercov -- uv run pytest
+npx supercov -- python -m unittest
+```
+
 ## Containers, VMs, and remote execution
 
 Supercov can collect from supported processes launched through a container, VM,

package/docs/workspace-isolation.md

@@ -32,7 +32,9 @@ synced back to the project after the run, so `supercov -- npm test -- -u`
 updates snapshots in the repository exactly as `npm test -- -u` would. Two
 exceptions are reported instead of applied: changes the command makes to
 instrumented source files (the instrumented copies must never overwrite your
-sources) and deletions (never propagated automatically).
+sources) and deletions (never propagated automatically). Changes inside any
+`node_modules` directory are neither applied nor reported: dependency trees are
+not command outputs.
 
 ## Files Supercov creates
 
@@ -88,6 +90,15 @@ When a suite launches a container or VM from a mounted workspace, Supercov uses
 the isolated workspace as the source presented to that environment. The runtime
 must be able to cross the launch boundary and return evidence.
 
+Dependencies stay out of the instrumented copy. The root `node_modules` is
+linked entry by entry to the project's own, so an environment that mounts the
+workspace must bring its own root dependencies (the supported launchers do).
+Nested `node_modules` inside packages and extensions are materialised as real
+directories: cloned copy-on-write where the filesystem allows it (APFS), and
+hard-linked file by file elsewhere on Unix, so they resolve inside the mount
+either way. Only when neither is possible, such as a dependency tree on another
+volume, are they linked entry by entry like the root.
+
 If a remote executor hides the launch or mount boundary, Supercov reports the
 limitation instead of claiming unseen code was measured. See
 [Supported suites](supported-suites.md) for the current boundary.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "supercov",
-  "version": "0.0.29",
-  "description": "Zero-edit, runner-aware coverage completeness for JavaScript test suites",
+  "version": "0.0.31",
+  "description": "Zero-edit, runner-aware coverage completeness for JavaScript, TypeScript, Rust, and Python test suites",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -62,18 +62,20 @@
     "test:clang-mcdc": "node scripts/clang-mcdc-oracle.mjs",
     "test:test262": "cargo build --release -p supercov && node scripts/test262-equivalence.mjs",
     "benchmark:check": "cargo build --release -p supercov && node scripts/rust-transform-benchmark.mjs",
+    "benchmark:python-monitoring": "cargo build -p supercov && node scripts/python-monitoring-benchmark.mjs",
     "check": "cargo fmt --all -- --check && cargo clippy --workspace --all-targets -- -D warnings && npm run test && npm run test:runtime && npm run test:rust-assets && node scripts/package-preflight.mjs",
-    "release:check": "npm run check && npm run test:engine && npm run test:fixture && npm run test:watchdog && npm run test:engine-contract && npm run test:agent && npm run test:packed-npx && npm run test:clang-mcdc && npm run benchmark:check",
+    "release:check": "npm run check && npm run test:engine && npm run test:fixture && npm run test:watchdog && npm run test:engine-contract && npm run test:agent && npm run test:python-monitoring && npm run test:packed-npx && npm run test:clang-mcdc && npm run benchmark:check",
     "prepack": "node scripts/package-preflight.mjs",
-    "prepublishOnly": "npm run release:check"
+    "prepublishOnly": "npm run release:check",
+    "test:python-monitoring": "cargo build -p supercov && node scripts/python-monitoring-integration.mjs"
   },
   "optionalDependencies": {
-    "@supercov/cli-darwin-arm64": "0.0.29",
-    "@supercov/cli-darwin-x64": "0.0.29",
-    "@supercov/cli-linux-arm64-gnu": "0.0.29",
-    "@supercov/cli-linux-arm64-musl": "0.0.29",
-    "@supercov/cli-linux-x64-gnu": "0.0.29",
-    "@supercov/cli-linux-x64-musl": "0.0.29"
+    "@supercov/cli-darwin-arm64": "0.0.31",
+    "@supercov/cli-darwin-x64": "0.0.31",
+    "@supercov/cli-linux-arm64-gnu": "0.0.31",
+    "@supercov/cli-linux-arm64-musl": "0.0.31",
+    "@supercov/cli-linux-x64-gnu": "0.0.31",
+    "@supercov/cli-linux-x64-musl": "0.0.31"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.55.0",