-
Notifications
You must be signed in to change notification settings - Fork 421
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.
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
--override
not supported by uv run
#4824
Comments
Thank you for writing it up in this detail! I agree that we likely want to support |
Thanks @konstin for validating my use-case! Indeed, And here is the proof in workflow execution: https://github.com/kdeldycke/click-extra/actions/runs/9806741540/job/27079121955#step:9:18 |
What would the target of |
I'd say |
Nothing of substance to say but I'll be happy either way! :) |
Using the latest
uv
:Use-case
I have a test workflow for my
click-extra
project which boils down to:Everything's good as it is.
But now I want to override some of the default dependencies specified in
pyproject.toml
. My use-case is to test unreleased upstream dependencies, so I can anticipate upcoming breaking changes.What I used to do with Poetry was to locally add these new dependencies as-is:
Migrating to
uv
, my new workflow looks like this:But this doesn't work as I expected. As soon as I call
uv run pytest
, the locally installed Click is discarded, and replaced by the canonical requirement frompyproject.toml
:See how I installed the
click==8.2.0.dev0
version I am looking for:And then have
uv run pytest
re-installing backclick==8.1.7
:--override
workaroundDigging into
uv
help, I stumble upon the--override
option, which seems to be the way to do what I want.So I now have:
And using it ends up with the right dependencies:
Which seems to do the trick. But again,
uv run
is reverting my override:--override
not supported byuv run
So maybe I need to use
--override
onuv run
. But it is not supported:Should we requalify this ticket into a feature request to have
--override
supported by therun
subcommand?New
--no-upgrade
option foruv run
?Another alternative is maybe to have a
--no-upgrade
option onuv run
to tell it to not make any changes to the currently installed dependencies.That might be the opposite of the existing
-U/--upgrade
parameter:The text was updated successfully, but these errors were encountered: