[tests env] swtich from pipenv to uv to handle python dependencies for tests #11317
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.
uv is the new kid around about package management https://docs.astral.sh/uv
it recently added a lock file that is cross OS
uv.lock
. This is not something we have with pipenv and it created issue recently (we needed to pin pipenv #11263)This should solve the problem, and uv is really fast !! So it could also maybe make our workflow faster.
This is PR is a first try at a switch to manage the project virtualenv in
tests/.venv
using uv on CI.I tested everything locally too, as I relied on pipenv myself. I don't know how the rest of the team is managing the python environment for tests, but this should make it a lot easier.
Once
uv
is installed on the system it is a matter ofcd tests/ uv sync
This
Then uv helps in upgrading dependencies, and adding one (stored in
pyproject.toml
Let's see if this helps.
Aims is also to see if Quarto 1.6 does works correctly with latest Python tooling.