This release is a pre-release and may not be stable for production use.
stubborn-watch
Debounced file watch → external SCIP indexer (scip-java) → stubborn index --merge.
Stubborn does not parse Java source. This package only orchestrates the dev loop described in ADR-009.
Install
pip install stubborn-watch
Requires scip-java on PATH for the default indexer command.
Usage
Watch mode (dev loop)
stubborn index --scip index.scip --out symbols.db # initial full snapshot
stubborn-watch watch --root . --db symbols.db
On save (debounced, default 2s):
scip-java indexstubborn index --mergefor changedrelative_pathvalues
One-shot merge (hooks / CI helpers)
stubborn-watch merge-once --root . --db symbols.db \
--paths com/example/Foo.java,com/example/Bar.java
Use --skip-index when index.scip is already fresh.
Workspace watch (multi-repo)
For source-available internal repos, use a workspace manifest so each repo can index and merge independently into one shared workspace DB:
{
"workspace": "acme",
"db": "symbols.db",
"repos": [
{ "repo_key": "orders-api", "root": "../orders-api", "scip": "index.scip" },
{ "repo_key": "orders-core", "root": "../orders-core", "scip": "index.scip" }
]
}
stubborn-watch workspace-watch --manifest stubborn-workspace.json
stubborn context symbols.db --workspace acme --target "<stable_id>"
Validation scope
This repo owns orchestration-focused validation:
- CLI smoke for
merge-once - debounce and path normalization
- subprocess invocation contracts around
scip-java
The canonical ADR-009 runnable demo lives in stubborn-demo:
That keeps stubborn-watch focused on watch behavior, while stubborn-demo owns runnable demo assets and black-box validation projects.
Options
| Flag | Default | Purpose |
|---|---|---|
--root |
. |
Project root |
--db |
(required) | SQLite symbol graph |
--scip |
index.scip |
SCIP index path |
--debounce |
2.0 |
Seconds to coalesce events |
--pattern |
**/*.java |
Watched file glob |
--scip-cmd |
scip-java index |
External indexer command |
--workspace |
— | Workspace name for repo-scoped merges |
--repo |
— | Repo key for repo-scoped merges |
Setup diagnostics
Read-only dev-loop prerequisites (ADR-015) — does not start watch or invoke scip-java:
stubborn-watch doctor --root . --db symbols.db
stubborn-watch doctor --json
Related
- stubborn — core compiler +
--merge - stubborn-mcp — MCP server over the same
symbols.db - stubborn-demo — runnable demos and validation projects
- stubborn-hub — program architecture
License
MIT — see LICENSE.
Metadata
Release files for stubborn-watch 0.10.0b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| stubborn_watch-0.10.0b2.tar.gz | 12.9 kB | Without provenance | Details for stubborn_watch-0.10.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stubborn_watch-0.10.0b2-py3-none-any.whl | Python 3 | none | any | Details for stubborn_watch-0.10.0b2-py3-none-any.whl |
Total release size: 26.0 kB
Release files / stubborn_watch-0.10.0b2.tar.gz
| Download URL | stubborn_watch-0.10.0b2.tar.gz |
|---|---|
| Size | 12.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c799dbc7f27d0642c00efeafdbe1209e7a629c78c41f8a1567f2ee0224821cb8
|
|
BLAKE2b-256 checksum How to use checksums |
0c473baf23fec79da1dd9aec7ea9227a4be4f6e6580a9973e16c1c76851a5aed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / stubborn_watch-0.10.0b2-py3-none-any.whl
| Download URL | stubborn_watch-0.10.0b2-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d76dc151beed5d398e6db06dc8527ab9b1af566453098b3f29975ed1f53b8ef9
|
|
BLAKE2b-256 checksum How to use checksums |
751ed46f1d30e704d63a01d3d2887d0a55c8776bec668ad2a5732587cc40b107
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for stubborn-watch 0.10.0b2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.