dummy support for uv-installed pythons #842
Open
+92
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A question more than a PR, now that
uv
supports bringing its own pythons, i wanted to try simplify a CI and not have to install python from other sources, butnox
is currently now able to find uv-installed pythons (someone else's issue @UV about this same thing astral-sh/uv#6579 )would it make sense to add a more fleshed out version of this? meaning passing the desired interpreter to
uv venv -p {interpreter}
, or should this be done by other mechanism that adds uv's python interpreters to$PATH
?note: this is just a draft to show an example, kind of works but also breaks tests and probably breaks
uv|virtualenv
and other things