-
Notifications
You must be signed in to change notification settings - Fork 14
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
Confused about how to use without a virtualenv #124
Comments
And if I put the path to the uv-managed python at the front of my PATH environment variable, and then try to install something into its environment with
|
The way I've worked around this is by activating the virtualenv once, then inserting the updated PATH into GITHUB_ENV:
It looks like the |
|
Ah, great, glad you were ultimately able to figure out what I meant. |
I agree it's a bit confusing, at the moment I'm going with:
But it doesn't seems like the recommended approach. |
I feel like I'm going against the grain here and maybe that's the issue.
I'd like to replace
setup-python
withsetup-uv
. Our existing CI usespython
fromsetup-python
directly, without setting up a virtualenv.Is it possible to use
uv
in a similar way? Basically, I'd like to install directly into the global environment associated with auv python install
command. When I try to actually do that, I see errors like:Is the right thing to do here to put uv's python at the front of the
PATH
and then pass--system
? Or just use a virtualenv? If it's the latter, then this is not quite a drop-in replacement for setup-python, since that's not necessary with setup-python.The text was updated successfully, but these errors were encountered: