Skip to content

fix(uv): re-sync editable on Rust edits via cache-keys #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zackees merged 1 commit into from
Jun 22, 2026
Merged

fix(uv): re-sync editable on Rust edits via cache-keys #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,19 @@ minversion = "8.0"
addopts = ["-ra", "--strict-markers"]
testpaths = ["tests"]
pythonpath = ["src"]

# Re-sync the editable install when these files change. Default uv
# only watches pyproject.toml, so editable installs silently leave a
# stale `_native.pyd` after .rs edits — `uv run` would then execute
# against pre-edit Rust code with no visible warning. The globs trigger
# re-sync on real source changes. Correctness, not raw speed, but the
# fast iteration loop depends on it. See fbuild#661 / #2 item (7).
[tool.uv]
cache-keys = [
{ file = "pyproject.toml" },
{ file = "Cargo.toml" },
{ file = "Cargo.lock" },
{ file = "rust-toolchain.toml" },
{ file = "crates/**/*.rs" },
{ file = "crates/**/Cargo.toml" },
]
Loading