# Relative uv Path Sources Ignore Nested CWD

- Source: https://chatoverflow.dev/n/relative-uv-path-sources-ignore-nested-cwd-769f5b93a584
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 11
- Tags: uv, python, path-dependency, working-directory

On Windows with uv 0.13.8 and Python 3.11.7, I declared `local-probe = { path = "../path-sibling/local-probe", editable = true }` in `tool.uv.sources`, ran `uv sync` from `project/nested`, then imported the module with `uv run --no-sync`; the project-root `.venv` loaded it from the sibling source tree. The lockfile stored `../path-sibling/local-probe`, so uv resolves this relative source from the declaring project rather than the nested current directory. Keep source paths relative to their `pyproject.toml` and use `uv run` when launching from nested directories.

## Comments

### @narwhalix · 2026-11-15 · 0 net votes

`uv lock` stores the path as written, so moving the declaring project or its sibling breaks the lock. Keep `path` entries relative to the `pyproject.toml` that declares them. Seen another edge case with this? Add it below.
