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

Cannot detect/specify kernel in WinPython environment #23293

Closed
1 of 2 tasks
4piu opened this issue Apr 23, 2024 · 7 comments
Closed
1 of 2 tasks

Cannot detect/specify kernel in WinPython environment #23293

4piu opened this issue Apr 23, 2024 · 7 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@4piu
Copy link

4piu commented Apr 23, 2024

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

I am using WinPython 3.12.2 environment on my Windows 11 machine, and launch VS Code through their provided shortcut.
I have no trouble setting up Python interpreter by manually specifying the python executable path:
image

However, notebook plugin cannot detect python environment (empty list), nor allow manually specifying path:
image
image

VS Code Version

1.88.1

Jupyter Extension Version

v2024.4.2024041101

Jupyter logs

No response

Coding Language and Runtime Version

WinPython 3.12.2

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Local

@4piu 4piu added the bug Issue identified by VS Code Team member as probable bug label Apr 23, 2024
@DonJayamanne
Copy link

Does python show up in the list of Python environments when using the command Python: Select Interpreter?

@DonJayamanne DonJayamanne added the info-needed Issue requires more information from poster label Apr 24, 2024
@4piu
Copy link
Author

4piu commented Apr 24, 2024

Does python show up in the list of Python environments when using the command Python: Select Interpreter?

No, the Python:Select Interpreter only shows the Python is not installed warning, and I have to use Enter interpreter path... to specify the interpreter.
Even after entering the path, the VS Code does not create an entry for it. (As the first screenshoot shows)

@4piu
Copy link
Author

4piu commented Apr 24, 2024

I also tried setting the python.defaultInterpreterPath, which adds an entry to Python: Select Interpreter, but the vscode-jupyter's Select Kernel > Python Environments... list is still empty.
image

@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-jupyter Apr 24, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 24, 2024
Copy link

github-actions bot commented Jun 7, 2024

Hey @karthiknadig, this issue might need further attention.

@4piu, you can help us out by closing this issue if the problem no longer exists, or adding more information.

Copy link

github-actions bot commented Jul 8, 2024

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
@karthiknadig karthiknadig reopened this Jul 8, 2024
@karthiknadig
Copy link
Member

@4piu Is the WinPython location on PATH? if it is not on path then it will be difficult for python extension to find it. Another option is to create a virtual environment in your workspace. You can use the WinPython, like <python path here> -m venv .venv in your workspace from a terminal. Python extension will detect and use this virtual environment for both running python files, and as python to use with Jupyter extension.

@karthiknadig
Copy link
Member

Closing as duplicate of microsoft/python-environment-tools#96

@karthiknadig karthiknadig closed this as not planned Won't fix, can't repro, duplicate, stale Jul 9, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

3 participants