Closed timstaley closed 3 months ago
-e.
is better, though it looks like even that isn't rebuild, so it wouldn't work well for a binary package (or when adding entry points, etc).
Would be a good thing to document until/if something changes upstream.
Current Behavior
I've just been experimenting with the new uv backend - it's super fast and seems to mostly just work, so much happiness around that :)
However, I hit a fair bit of confusion when running some code via nox and seeing outdated results compared to my IDE. Swapping backend between
venv
anduv
confirms this is becauseuv
is using a cached (outdated) version of my local package, when it should be rebuilding from the source. (Possibly related to this issue? https://github.com/astral-sh/uv/issues/2844)Anyhow, I can fix this if I replace
with
I'm guessing that whether or not this should 'just work' is an upstream issue for the UV folks, but maybe it's worth a note in the Nox docs around UV usage - I imagine this will be a pretty common failure case.
Expected Behavior
With the setting
Installing my package under development into a nox-env via
I expected the same behaviour as plain pip /
venv
- rebuild and install the latest version of my package from source.Instead; I get the version of my package from when I first switched backend to
uv
, because it's caching the build.Steps To Reproduce
No response
Environment
Anything else?
No response