[Python] Venv tweaks based on testing in Sandboxes #2264
Merged
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.
Summary
A few small tweaks after testing in Sandboxes
STATE_CHECK
to after we verify that a VENV exists and that it's properly formatted. This ensures that we can fix scenarios where the venv was deleted or broken, without excessively prompting the userUV_PYTHON
environment variable to ensure that users who installuv
don't accidentally overwrite the Python version in theirdevbox.json
How was it tested?
python-flask
Jetify Example in Sandboxes.venv
is setup correctly withdevbox shell
.venv
dir, verify that re-runningdevbox shell
creates ituv
(devbox add uv
)uv sync
and other commands don't override Devbox Python