Skip to content

Filenames identified by WindowsPathEnvVarLocator have an unexpected format. #15289

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

Closed
ericsnowcurrently opened this issue Feb 1, 2021 · 0 comments · Fixed by #15483
Closed
Assignees
Labels
area-environments Features relating to handling interpreter environments debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority

Comments

@ericsnowcurrently
Copy link

ericsnowcurrently commented Feb 1, 2021

Locators on WIndows have consistently provided executable filenames with ~ unexpanded and with case matching whatever the OS reported. However, executables located by WindowsPathEnvVarLocator are all lower-cased and ~ is expanded. It would probably make sense to get WindowsPathEnvVarLocator consistent with the other locators.

image

(See #15177 (comment).)

@ericsnowcurrently ericsnowcurrently added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. area-environments Features relating to handling interpreter environments labels Feb 1, 2021
@karrtikr karrtikr added the important Issue identified as high-priority label Feb 23, 2021
@karrtikr karrtikr self-assigned this Feb 23, 2021
@ghost ghost removed the needs PR label Feb 23, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants