Using python -m venv for Venv Creation for UV Lock Scenarios#2829
Open
prathambande wants to merge 1 commit intomainfrom
Open
Using python -m venv for Venv Creation for UV Lock Scenarios#2829prathambande wants to merge 1 commit intomainfrom
prathambande wants to merge 1 commit intomainfrom
Conversation
larohra
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, for pyproject.toml and uv.lock combination-based python oryx build, venv created is using
uv venv. Venv created in such fashion has python bin in it as a symlink (Open Issue) which poses problems when transporting environments between build and runtime stages.This PR fixes it by using
python -m venvfor venv creation instead.Note:
uvis still used for package installation for these scenarios (uv pip install,uv sync) when appropriate.