fix: don’t print warning about upgrading the venv if the venv wasn’t upgraded yet - #1150
Merged
jenstroeger merged 1 commit intoMay 25, 2026
Merged
fix: don’t print warning about upgrading the venv if the venv wasn’t upgraded yet#1150jenstroeger merged 1 commit into
jenstroeger merged 1 commit into
Conversation
Copy link
Copy Markdown
Owner
Sorry, something went wrong.
jenstroeger
force-pushed
the
fix-makefile-6
branch
from
b024ccd to
6b89301
Compare
April 24, 2026 01:51
behnazh
approved these changes
May 1, 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
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.
If the file .venv/upgraded-on doesn’t exist (e.g. new venv) then don’t attempt to compare timestamps with that non-existing file, which only leads to a confusing warning.