"Python: Locator" = "native" resolves Windows symlinks, causing problems.

[Boon-in-Oz]

My Python executable and most of the packages I work on are physically located on drive S:, but are mapped to a location on my C:\ drive using a Windows junction. Thus I open a workspace using a path that starts with C:\ and everything I see starts with C:, even though all the files I work on are physically on my S:\ drive.

With "Python: Locator" = "js", this is fine. I have this line of in VS Code's Python output:

[info] Python interpreter path: c:<my workspace location>/../python3.10.11/python.exe

With "Python: Locator" = "native" however, VS Code's Python extension resolves not only the .. in the path but also the junction to its physical location on the S:\ drive. I now have this in the Python output:

[info] Python interpreter path: S:<resolved location>\python3.10.11\python.exe

VS Code shows (in the tooltip in the bottom right) the Python exe being in the S:\ drive location. If I choose a new Python interpreter, the interpreter location is shown as being in the C:\ drive but when I choose it, it's resolved to the S:\ drive again.

Specifically in my case this results in dlls being loaded from the wrong location, that then try to manipulate files using a path that is outside the "blessed" location for my workplace, and things fail in unexpected ways.

Thanks for your time. I hope that's enough to go on.

[DonJayamanne]

Sorry you are running into this issue & thanks for reporting this issue.

interpreter, the interpreter location is shown as being in the C:\ drive but when I choose it, it's resolved to the S:\ drive again.

Can you tell me what you get when you run this code in the terminal

c:<my workspace location>/../python3.10.11/python.exe -c "import sys;print(sys.executable)"

[Boon-in-Oz]

I should note that my workspace is a multi-root workspace, so the Python "defaultInterpreterPath" looks like this:
"python.defaultInterpreterPath": "${workspaceFolder:packages}/../python3.10.11/python.exe"

Substituting in my "packages" directory path into your command above, I get the correct result on the C:\ drive with the .. resolved but the symlink ignored.

c:/<my packages dir path>/../python3.10.11/python.exe -c "import sys;print(sys.executable)"
C:\<etc>\python3.10.11\python.exe

The "Python: locator" setting doesn't seem to affect the result.

[DonJayamanne]

The "Python: locator" setting doesn't seem to affect the result.

Not sure what you mean by this, I thought with native the result was different.
Or is it not?

[Boon-in-Oz]

I may have made a mistake there, sorry. I'm at home now. I'll update you tomorrow.

[Boon-in-Oz]

OK here we go. I've run that same code in a terminal and via "Run Python File" on the right-click menu, with both settings of "Python: Locator":

1. Locator: js, right click on a .py file and run via "Run Python File":

import sys
print(sys.executable)
> C:\<my path>\python3.10.11\python.exe

2. Locator: js, from terminal:

c:/<my path>/packages/../python3.10.11/python.exe -c "import sys;print(sys.executable)"
> C:\<my path>\python3.10.11\python.exe

3. Locator: native, right-click on a .py file and run via "Run Python File":

import sys
print(sys.executable)
> S:\<resolved path>\python3.10.11\python.exe

4. Locator: native, from terminal:

c:/<my path>/packages/../python3.10.11/python.exe -c "import sys;print(sys.executable)"
> C:\<my path>\python3.10.11\python.exe

[DonJayamanne]

Thank you , please can you share the logs from Python and Python Locator as follows

• Open VS Code
• Go into the command palette and select the command Developer: Set Log Level
• Select Trace from the dropdown list
• Reload VS Code
• Next from the command palette select the command Python: Select Interpreter
• Go into the logs from Output> Python Locator and share all of the logs (this time there will be more information)
• Go into the logs from Output> Python and share all of the logs (this time there will be more information)

You can get to the logs using the command Python: Show Output
From there you can use the dropdown in the output panel (right hand side) to select the Python Locator logs.

Please share both the logs

[Boon-in-Oz]

Here you go.
For the "Reload VS Code" step I went with the command "Developer: Reload Window", as restarting VS Code was resetting the log level.

trace_python_locator.txt
trace_python.txt

[DonJayamanne]

@Boon-in-Oz Thank you for the logs and apologies for the delay in getting back to you.
Please can you open a terminal outside VS Code.
Run the following in your terminal and let me know what you get

c:\\project\\bin\\lang\\techart\\python3.10.11\\python.exe -c "import sys;print(sys.executable)"

[DonJayamanne]

@Boon-in-Oz what kind of Python environment is this?
More specifically how did you install this Python environment. Asking as it doesn't seem to have the standard scripts/bin directory for the Python exe.

[Boon-in-Oz]

You're correct, it's unusual! I'm on a team that supports people working in 3DS Max, Maya and Substance Painter. We use Perforce to distribute all our tools, including Python, so we have copies of Python 3.9, 3.10 and 3.11 in local directories.

When I enter the call above in a Windows Command Prompt, I get

c:\project\bin\lang\techart\python3.10.11\python.exe

[DonJayamanne]

I think I know whats going on,
Will create a new version with some additional logging.
Hopefully you can install that new version and share the logs
Will get back with details once i'm ready

[DonJayamanne]

@Boon-in-Oz I have a new version of Python extension with some more logging
Please can you install the latest pre-release version of Python extension (version 2025.7.*)
Reload VS Code, and share the logs again as per instructions here #186 (comment)

Thank you