Skip to content
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

Python Interpreter change not working in Windows #6

Open
MilkClouds opened this issue Nov 14, 2024 · 9 comments
Open

Python Interpreter change not working in Windows #6

MilkClouds opened this issue Nov 14, 2024 · 9 comments

Comments

@MilkClouds
Copy link

Describe the bug
Python Interpreter change not working in Windows

To Reproduce

  1. Command Palette
  2. pixi change interpreter
pixi-vscode: Python interpreter path does not exist: (skipped directory)\.pixi\envs\default/bin/python You might need to pixi install -e default

Desktop (please complete the following information):

  • OS: [e.g. iOS] Windows 23H2
  • pixi vscode extension version v1.0.0 preview
  • python vscode extension version v2024.20.0
  • vscode version
$ code -v
1.95.2
e8653663e8840adaf45af01eab5c627a5af81807
x64

Please fix this issue also in vscode python extension, if it have same issue.

@MilkClouds
Copy link
Author

{C697C18D-87E9-4AF3-903B-05D2239997AC}
I guess here is the bad part

@jjjermiah
Copy link
Owner

yeah looks like its not OS-agnostic. Will address this asap. Thanks!

@jjjermiah
Copy link
Owner

@MilkClouds try updating the newest version and let me know if that works

@MilkClouds
Copy link
Author

MilkClouds commented Nov 15, 2024

@jjjermiah nope it causes similar error because python.exe's path is .pixi/envs/default/python.exe, not .pixi/envs/default/bin/python.exe (I don't know why though.... but I didn't touch anything and it is default setting)

@MilkClouds
Copy link
Author

{1CA64CCF-A983-4368-AC2A-65F3250537B5}

@MilkClouds
Copy link
Author

{8F16572B-A6B5-4280-B8FE-B756031AB012}

@jjjermiah
Copy link
Owner

hi @MilkClouds does this work for you ?

@MilkClouds
Copy link
Author

2025-01-23 13:50:43.891 [error] getActivatedEnvironmentVariables Error: Command failed: conda run -n default --no-capture-output python c:\Users\MilkClouds\.vscode\extensions\ms-python.python-2024.22.2-win32-x64\python_files\get_output_via_markers.py c:/Users/MilkClouds/.vscode/extensions/ms-python.python-2024.22.2-win32-x64/python_files/printEnvVariables.py

EnvironmentLocationNotFound: Not a conda environment: C:\Users\MilkClouds\miniforge3\envs\default


    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at ChildProcess.exithandler (node:child_process:423:12)
    at ChildProcess.emit (node:events:530:35)
    at maybeClose (node:internal/child_process:1104:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'conda run -n default --no-capture-output python c:\\Users\\MilkClouds\\.vscode\\extensions\\ms-python.python-2024.22.2-win32-x64\\python_files\\get_output_via_markers.py c:/Users/MilkClouds/.vscode/extensions/ms-python.python-2024.22.2-win32-x64/python_files/printEnvVariables.py'
}

it's not working yet!

@MilkClouds
Copy link
Author

it was resolved by updating ms-python.python extension; related issue is on microsoft/vscode-python#24569.
Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants