Repository navigation
Pyenv to uv - #193
Merged
Merged
Pyenv to uv#193
Conversation
By default fall back to the globally installed lewagon venv. Inside projects, it will activate the in-project venv.
This allows to just do `git push` to push the local branch to origin.
gmanchon
self-requested a review
September 21, 2026 14:27
gmanchon
approved these changes
Sep 21, 2026
gmanchon
left a comment
gmanchon
left a comment
Contributor
There was a problem hiding this comment.
LGTM, let's merge when data setup pyenv to uv is merged lewagon/data-setup#374
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.
Changes related to the switch to
uv:pyenvlines to avoid conflicts. Don't remove to allow students / alumni to easily set them back.venvby default, and set the prompt exactly the same as we are used to. This checks for the existence of the folder, so doesn't break if there is novenvthere.venvby default, but also set VS Code to activate an in-projectvenvif there is one. Important for MLOps and projects.No impact on existing setups: in principle students / alumni have their own fork. As long as they don't
pull upstream, they will keep their existing setup.Unrelated: set autoSetupRemote to true in gitconfig so we can just
git pushi.o.git push origin master.Created a
master-pyenvbranch to allow easy switching to apyenvbased setup if needed.