fix: Avoid symlinks for user-docs venv creation #73
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.
There was/is an issue with the creation and caching of the Python virtual environment.
When we create it with
uv
orpython3 -m venv
, thepython
executable is only linked to the system's Python installation.This symlink is not properly cached in the GitHub cache action.
The workaround is to use the
--copies
flag forvenv
, however there is no equivalent flag foruv
, although there is a similar one for linking cached Python libraries (--link-mode
).Unless astral-sh/uv#6782 is fixed soon, we have to live with the workaround of using good old
venv
.P.S.: the build still fails for this PR as we are using
pull_request_target
.