fastws-cli 0.0.7__tar.gz → 0.0.9__tar.gz

fastws_cli-0.0.9/CHANGELOG.md

@@ -0,0 +1,59 @@
+<!-- do not remove -->
+
+## 0.0.9
+
+### New Features
+
+- Add ws-build: build sdists of all workspace projects into a dists dir, skipping unchanged projects and pruning old versions ([#23](https://github.com/AnswerDotAI/fastws/issues/23))
+- detect project from cwd, add --nodeps to skip the dependency closure, and map dir names to packages ([#22](https://github.com/AnswerDotAI/fastws/issues/22))
+- Move `dep_key`, member graph, and closure helpers to ghapi (>=2.0.6) and use `dep_key`/`local_dep_graph`/`dep_closure` in core and releases ([#21](https://github.com/AnswerDotAI/fastws/issues/21))
+- ws-sync: write content-hashed .git/fastws-cargo-key per crate, covering Cargo.lock and locally patched git deps, for uv cache-keys ([#20](https://github.com/AnswerDotAI/fastws/issues/20))
+- Run cargo update before uv sync in `ws_sync` so Rust deps refresh first ([#19](https://github.com/AnswerDotAI/fastws/issues/19))
+- Add out-of-tree repo support, auto-managed workspace excludes, and uv.sources preservation to ws-sync ([#18](https://github.com/AnswerDotAI/fastws/issues/18))
+
+
+## 0.0.8
+
+### New Features
+
+- Add ws-releases: report unreleased commits across the workspace, with configurable skip patterns and repo exclusions ([#17](https://github.com/AnswerDotAI/fastws/pull/17)), thanks to [@jph00](https://github.com/jph00)
+- Add once-daily dependency floating to ws_sync (uv sync -U + cargo update), with --upgrade flag to force ([#15](https://github.com/AnswerDotAI/fastws/issues/15))
+- ws-sync skips uv sync for member dirs lacking pyproject.toml; ws-add resolves local folder names via origin remote ([#12](https://github.com/AnswerDotAI/fastws/issues/12))
+- Allow bare folder name in ws-remove; separate directory deletion confirmation from metadata removal ([#9](https://github.com/AnswerDotAI/fastws/issues/9))
+- Add `ws-remove` command to delete a repo from the workspace; refactor CLI wrappers with `@delegates` ([#8](https://github.com/AnswerDotAI/fastws/issues/8))
+- Add [dev] extra to workspace dependencies and filter spurious warnings ([#7](https://github.com/AnswerDotAI/fastws/pull/7)), thanks to [@RensDimmendaal](https://github.com/RensDimmendaal)
+- add --workers flag to ws-sync ([#6](https://github.com/AnswerDotAI/fastws/pull/6)), thanks to [@RensDimmendaal](https://github.com/RensDimmendaal)
+
+### Bugs Squashed
+
+- Preserving existing tool.uv.sources entries during ws-sync ([#14](https://github.com/AnswerDotAI/fastws/pull/14)), thanks to [@kafkasl](https://github.com/kafkasl)
+
+
+## 0.0.7
+
+### New Features
+
+- Refactor Pyright editable path setup to write pyrightconfig.json instead of .pth files ([#4](https://github.com/AnswerDotAI/fastws/issues/4))
+
+
+## 0.0.6
+
+### New Features
+
+- Add root-aware clone/pull helpers, auto-pull in ws-sync, and docstrings to CLI entry points ([#2](https://github.com/AnswerDotAI/fastws/issues/2))
+
+
+## 0.0.5
+
+### New Features
+
+- Add ws-sync and ws-add commands with workspace metadata sync and Pyright editable path support ([#1](https://github.com/AnswerDotAI/fastws/issues/1))
+
+
+## 0.0.3
+
+- change names
+
+## 0.0.2
+
+- init release

fastws_cli-0.0.9/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: fastws-cli
+Version: 0.0.9
+Summary: Fast workspace tools for multi-repo management
+Author: Jeremy Howard
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/AnswerDotAI/fastws
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: fastcore>=1.14.3
+Requires-Dist: fastgit>=0.0.7
+Requires-Dist: ghapi>=2.0.6
+Requires-Dist: packaging
+Requires-Dist: tomli; python_version < "3.11"
+Provides-Extra: dev
+Requires-Dist: fastship; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Dynamic: license-file
+
+# fastws
+
+Fast workspace tools for multi-repo management.
+
+## Install
+
+```bash
+pip install fastws-cli
+```
+
+## Setup
+
+Create a `repos.txt` file listing your repos (one per line):
+
+```
+AnswerDotAI/fastcore
+AnswerDotAI/fastgit
+AnswerDotAI/fastship
+AnswerDotAI/fastws
+```
+
+A line may add a checkout location after the repo, for repos that live outside
+the workspace root (`~` ok). Every command then reads and writes them there, and
+`ws-sync` editable-installs each Python project found inside (the repo root if it
+has a `pyproject.toml`, else its immediate subdirectories), so one out-of-tree
+repo can hold several small packages alongside non-Python content:
+
+```
+AnswerDotAI/fastcore
+jph00/private ~/private
+```
+
+## Commands
+
+### `ws-clone`
+
+Clone all repos from your repos file:
+
+```bash
+ws-clone
+ws-clone --repos-file myrepos.txt
+ws-clone --workers 8
+```
+
+### `ws-pull`
+
+Pull updates for all repos (parallel):
+
+```bash
+ws-pull
+```
+
+### `ws-status`
+
+Show uncommitted changes and unpushed commits:
+
+```bash
+ws-status
+ws-status --branches
+```
+
+### `ws-branches`
+
+Check if all repos are on the expected branch:
+
+```bash
+ws-branches
+ws-branches --expected develop
+```
+
+### `ws-build`
+
+Build an sdist of each workspace project (including `repos.txt` checkouts outside the root) into a dists directory, `.dists` by default. A project is rebuilt only when a file in it is newer than its existing sdist, and older versions of a rebuilt package are pruned, so the directory always holds one current sdist per project. A failing project gets a warning without stopping the others, but the command then exits 1.
+
+Progress goes to stderr; on success the dists path prints to stdout, so `$(ws-build)` in a script both refreshes the pool and yields its location. The result suits any resolver that takes a candidate pool, e.g. `uv pip install --find-links` or a docker build context for images that must test unreleased workspace packages:
+
+```bash
+ws-build
+ws-build --force  # rebuild everything
+ws-build --out /tmp/dists
+```
+
+### `ws-sync`
+
+Sync the workspace metadata, pull local repos, and install updates.
+By default it uses the active venv parent as the workspace root, so you do not need to `cd` first.
+It respects `tool.uv.workspace.members` and `exclude` when scanning local projects, and if any
+member directory isn't a Python project yet (no `pyproject.toml`, e.g. a fresh empty clone), it
+warns and skips the `uv sync` step instead of letting uv fail on the whole workspace.
+
+The workspace `exclude` list is auto-managed: a top-level directory that isn't a valid Python
+project and isn't a `repos.txt` checkout gets excluded automatically, and is un-excluded once it
+gains a real `pyproject.toml`. Globs, entries for missing directories, and entries for `repos.txt`
+checkouts are always kept, and `exclude = [...]` under `[tool.fastws]` in the workspace
+`pyproject.toml` declares intent the scan can't infer (e.g. keeping a real project out of the
+workspace). Hand-written `[tool.uv.sources]` entries (path, git, ...) are preserved when syncing
+adds new members.
+
+At most once per day (tracked by a stamp file inside the workspace's `.git`, so git never
+sees it), the sync also floats dependencies: `uv sync -U` instead of plain `uv sync`, plus
+a parallel `cargo update` in every member with a `Cargo.toml`, printing what moved. Pass
+`--upgrade` to force that pass regardless of when it last ran.
+
+Before every uv sync, `ws-sync` writes `.git/fastws-cargo-key` for each member crate. The key hashes `Cargo.lock` contents and the workspace Cargo patch configuration. For Git dependencies redirected to local paths by `[patch."<url>"]`, it also hashes each patched crate's `Cargo.toml`, `build.rs`, and `src` tree, recursively. The file is rewritten only when that content changes, so projects can use `{ file = ".git/fastws-cargo-key" }` in `tool.uv.cache-keys` without rebuilding after a timestamp-only `Cargo.lock` write.
+
+```bash
+ws-sync
+ws-sync --workspace ~/aai-ws
+ws-sync --upgrade
+```
+
+### `ws-add`
+
+Add a repo to `repos.txt`, then run `ws-sync`. Given `owner/repo`, it clones; given the
+name of an existing local folder (e.g. one just scaffolded with `nbdev-new` or `ship-new`),
+it resolves `owner/repo` from the folder's `origin` remote instead, telling you exactly
+what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`.
+Given a path outside the workspace root, the repo stays where it is and its location is
+recorded in `repos.txt` (no root `pyproject.toml` needed: its packages are discovered on sync):
+
+```bash
+ws-add AnswerDotAI/fastws
+ws-add answerdotai/fastws
+ws-add fastws  # existing local folder, resolved via its origin remote
+ws-add ~/private  # a path outside the workspace: stays where it is, recorded in repos.txt with its location
+```
+
+### `ws-remove`
+
+Remove a repo: delete its clone, and drop it from `repos.txt` and the workspace
+`pyproject.toml`, then run `uv sync`. It refuses if the directory has uncommitted
+changes, unpushed commits, no `origin` remote, or isn't a clean git checkout, and
+always prompts for confirmation before deleting anything:
+
+```bash
+ws-remove AnswerDotAI/fastws
+ws-remove fastws  # bare folder name also works if the directory exists
+```
+
+### `ws-releases`
+
+Report repos with commits since their newest GitHub release, so nothing reviewed sits unshipped:
+
+```bash
+ws-releases                 # at the workspace root: sweep every repo in repos.txt
+ws-releases solveit         # only solveit's transitive workspace dependencies
+ws-releases --nodeps        # inside a repo: just that repo
+ws-releases --skip 'wip'    # extra start-of-message regex for commits that need no release
+```
+
+Run from inside a workspace checkout, the sweep narrows to that repo and its transitive workspace dependencies; `--nodeps` narrows it to the repo alone (an error when no project is in play).
+
+Each pending repo lists its unreleased commit summaries; repos with no releases yet get one quiet `no releases:` line, and fully-released repos appear in `up to date:`. The newest release is picked by version number (publish timestamps can be out of order), and repos whose default branch isn't `main` are handled automatically.
+
+Commits whose message matches a start-anchored regex from the skip set need no release and aren't reported. The built-in set covers version bumps and housekeeping (`bump`, `nbdev regen`, `.gitignore`, `docs`, `CI`, ...: `DEFAULT_SKIP` in `fastws.releases`); `[tool.fastws]` in the workspace root `pyproject.toml` adds to it, and names repos that should never be swept (apps that deploy rather than release):
+
+```toml
+[tool.fastws]
+release_skip = ["docs only"]
+release_exclude = ["solveit", "md_site"]
+```
+
+From Python (the primary interface - the CLI is a thin wrapper over `fastws.releases`):
+
+```python
+from fastws import check_releases, check_release
+await check_releases()            # ReleaseReport: the repr is the report
+await check_releases('solveit')   # dependency-closure mode
+await check_release('mdhtml')     # one repo: list of unreleased commit summaries (None = no releases)
+```

fastws_cli-0.0.9/README.md

@@ -0,0 +1,170 @@
+# fastws
+
+Fast workspace tools for multi-repo management.
+
+## Install
+
+```bash
+pip install fastws-cli
+```
+
+## Setup
+
+Create a `repos.txt` file listing your repos (one per line):
+
+```
+AnswerDotAI/fastcore
+AnswerDotAI/fastgit
+AnswerDotAI/fastship
+AnswerDotAI/fastws
+```
+
+A line may add a checkout location after the repo, for repos that live outside
+the workspace root (`~` ok). Every command then reads and writes them there, and
+`ws-sync` editable-installs each Python project found inside (the repo root if it
+has a `pyproject.toml`, else its immediate subdirectories), so one out-of-tree
+repo can hold several small packages alongside non-Python content:
+
+```
+AnswerDotAI/fastcore
+jph00/private ~/private
+```
+
+## Commands
+
+### `ws-clone`
+
+Clone all repos from your repos file:
+
+```bash
+ws-clone
+ws-clone --repos-file myrepos.txt
+ws-clone --workers 8
+```
+
+### `ws-pull`
+
+Pull updates for all repos (parallel):
+
+```bash
+ws-pull
+```
+
+### `ws-status`
+
+Show uncommitted changes and unpushed commits:
+
+```bash
+ws-status
+ws-status --branches
+```
+
+### `ws-branches`
+
+Check if all repos are on the expected branch:
+
+```bash
+ws-branches
+ws-branches --expected develop
+```
+
+### `ws-build`
+
+Build an sdist of each workspace project (including `repos.txt` checkouts outside the root) into a dists directory, `.dists` by default. A project is rebuilt only when a file in it is newer than its existing sdist, and older versions of a rebuilt package are pruned, so the directory always holds one current sdist per project. A failing project gets a warning without stopping the others, but the command then exits 1.
+
+Progress goes to stderr; on success the dists path prints to stdout, so `$(ws-build)` in a script both refreshes the pool and yields its location. The result suits any resolver that takes a candidate pool, e.g. `uv pip install --find-links` or a docker build context for images that must test unreleased workspace packages:
+
+```bash
+ws-build
+ws-build --force  # rebuild everything
+ws-build --out /tmp/dists
+```
+
+### `ws-sync`
+
+Sync the workspace metadata, pull local repos, and install updates.
+By default it uses the active venv parent as the workspace root, so you do not need to `cd` first.
+It respects `tool.uv.workspace.members` and `exclude` when scanning local projects, and if any
+member directory isn't a Python project yet (no `pyproject.toml`, e.g. a fresh empty clone), it
+warns and skips the `uv sync` step instead of letting uv fail on the whole workspace.
+
+The workspace `exclude` list is auto-managed: a top-level directory that isn't a valid Python
+project and isn't a `repos.txt` checkout gets excluded automatically, and is un-excluded once it
+gains a real `pyproject.toml`. Globs, entries for missing directories, and entries for `repos.txt`
+checkouts are always kept, and `exclude = [...]` under `[tool.fastws]` in the workspace
+`pyproject.toml` declares intent the scan can't infer (e.g. keeping a real project out of the
+workspace). Hand-written `[tool.uv.sources]` entries (path, git, ...) are preserved when syncing
+adds new members.
+
+At most once per day (tracked by a stamp file inside the workspace's `.git`, so git never
+sees it), the sync also floats dependencies: `uv sync -U` instead of plain `uv sync`, plus
+a parallel `cargo update` in every member with a `Cargo.toml`, printing what moved. Pass
+`--upgrade` to force that pass regardless of when it last ran.
+
+Before every uv sync, `ws-sync` writes `.git/fastws-cargo-key` for each member crate. The key hashes `Cargo.lock` contents and the workspace Cargo patch configuration. For Git dependencies redirected to local paths by `[patch."<url>"]`, it also hashes each patched crate's `Cargo.toml`, `build.rs`, and `src` tree, recursively. The file is rewritten only when that content changes, so projects can use `{ file = ".git/fastws-cargo-key" }` in `tool.uv.cache-keys` without rebuilding after a timestamp-only `Cargo.lock` write.
+
+```bash
+ws-sync
+ws-sync --workspace ~/aai-ws
+ws-sync --upgrade
+```
+
+### `ws-add`
+
+Add a repo to `repos.txt`, then run `ws-sync`. Given `owner/repo`, it clones; given the
+name of an existing local folder (e.g. one just scaffolded with `nbdev-new` or `ship-new`),
+it resolves `owner/repo` from the folder's `origin` remote instead, telling you exactly
+what's missing if the folder has no git repo, no GitHub origin, or no `pyproject.toml`.
+Given a path outside the workspace root, the repo stays where it is and its location is
+recorded in `repos.txt` (no root `pyproject.toml` needed: its packages are discovered on sync):
+
+```bash
+ws-add AnswerDotAI/fastws
+ws-add answerdotai/fastws
+ws-add fastws  # existing local folder, resolved via its origin remote
+ws-add ~/private  # a path outside the workspace: stays where it is, recorded in repos.txt with its location
+```
+
+### `ws-remove`
+
+Remove a repo: delete its clone, and drop it from `repos.txt` and the workspace
+`pyproject.toml`, then run `uv sync`. It refuses if the directory has uncommitted
+changes, unpushed commits, no `origin` remote, or isn't a clean git checkout, and
+always prompts for confirmation before deleting anything:
+
+```bash
+ws-remove AnswerDotAI/fastws
+ws-remove fastws  # bare folder name also works if the directory exists
+```
+
+### `ws-releases`
+
+Report repos with commits since their newest GitHub release, so nothing reviewed sits unshipped:
+
+```bash
+ws-releases                 # at the workspace root: sweep every repo in repos.txt
+ws-releases solveit         # only solveit's transitive workspace dependencies
+ws-releases --nodeps        # inside a repo: just that repo
+ws-releases --skip 'wip'    # extra start-of-message regex for commits that need no release
+```
+
+Run from inside a workspace checkout, the sweep narrows to that repo and its transitive workspace dependencies; `--nodeps` narrows it to the repo alone (an error when no project is in play).
+
+Each pending repo lists its unreleased commit summaries; repos with no releases yet get one quiet `no releases:` line, and fully-released repos appear in `up to date:`. The newest release is picked by version number (publish timestamps can be out of order), and repos whose default branch isn't `main` are handled automatically.
+
+Commits whose message matches a start-anchored regex from the skip set need no release and aren't reported. The built-in set covers version bumps and housekeeping (`bump`, `nbdev regen`, `.gitignore`, `docs`, `CI`, ...: `DEFAULT_SKIP` in `fastws.releases`); `[tool.fastws]` in the workspace root `pyproject.toml` adds to it, and names repos that should never be swept (apps that deploy rather than release):
+
+```toml
+[tool.fastws]
+release_skip = ["docs only"]
+release_exclude = ["solveit", "md_site"]
+```
+
+From Python (the primary interface - the CLI is a thin wrapper over `fastws.releases`):
+
+```python
+from fastws import check_releases, check_release
+await check_releases()            # ReleaseReport: the repr is the report
+await check_releases('solveit')   # dependency-closure mode
+await check_release('mdhtml')     # one repo: list of unreleased commit summaries (None = no releases)
+```

fastws_cli-0.0.9/fastws/__init__.py

@@ -0,0 +1,8 @@
+__version__ = "0.0.9"
+
+
+
+
+from .core import *
+from .releases import *
+