-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
bpo-45337: Use the realpath of the new executable when creating a venv on Windows #28663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fe6aaf7
bpo-45337: Use the realpath of the new executable when creating a ven…
zooba 49fa664
Check against realpath on Windows
zooba 4f2ba18
Normalise path case before comparing strings
zooba eadb3cd
Better way to normalise case
zooba 283fc82
Merge branch 'main' into bpo-45337
zooba 642720d
Improve obviousness of new member
zooba File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
4 changes: 4 additions & 0 deletions
4
Misc/NEWS.d/next/Windows/2021-09-30-23-17-27.bpo-45337.qg7U_h.rst
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
venv now warns when the created environment may need to be accessed at a | ||
different path, due to redirections, links or junctions. It also now | ||
correctly installs or upgrades components when the alternate path is | ||
required. |
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 a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible that
sys.executable
will be called something other thanpython.exe
? Perhapspython3.exe
? AFAIK onlypython.exe
andpythonw.exe
will be added to the venv being created.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be.
python_d.exe
is the only one we support upstream, but I'd like it to be viable with other names (I have some private builds with alternate executable names).But right now it doesn't work anyway. The venv launcher executable has hardcoded names in it, so it'll only work as
python.exe
,python_d.exe
,pythonw.exe
andpythonw_d.exe
. Which means that this test is basically correct, unless we one day start running our test suite with a different executable name.