Filenames identified by WindowsPathEnvVarLocator have an unexpected format. #15289
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
Locators on WIndows have consistently provided executable filenames with
~
unexpanded and with case matching whatever the OS reported. However, executables located byWindowsPathEnvVarLocator
are all lower-cased and~
is expanded. It would probably make sense to getWindowsPathEnvVarLocator
consistent with the other locators.(See #15177 (comment).)
The text was updated successfully, but these errors were encountered: