Closed zacps closed 22 hours ago
+1 to this. Facing same issue but on a remotely running Jupyter.
@hnry-m When you say remotely running Jupyter, are you connecting to a Jupyter server (not VS Code) thats running on a different machine? If thats the case, please file a separate issue, this is not an issue with remote and unlikely to be related.
@zacps Thank you for filing this issue.
It looks like you have selected a Jupyter kernel, however the kernel points to python
instead of pointing to the fully qualified path to the python exe.
Suggestions, please can you select a Python Environment instead of selecting the Jupyter Kernel and try that. The reason this would happen is if you have Python installed in some non-global location or the like and Python is not in your current PATH.
This broke suddenly, without any obvious changes on my part (as far as I know).
Most likely cause is python
is no longer in your PATH (env variable)
Or you have selected Jupyter Kernel
instead of selecting a Python Environment.
@DonJayamanne python is, and always has been, available in PATH. I realised after posting this issue it occurs only in one folder (implicit workspace).
There are no settings configured differently as far as I know, except for these:
{
"python.testing.pytestArgs": [
"tests"
],
"python.testing.pytestEnabled": true,
"python.testing.unittestEnabled": false
}
which shouldn't make any difference and change nothing if removed.
The environment I want to use is a local virtual environment., but none other than one old explicitly registered kernel work.
I imagine the problem is due to the broken path /home/~/.vscode/extensions/ms-toolsai.jupyter-2024.5.0-linux-x64/dist/...
referred to in the logs.
+1 to issue. encountered while using jupyter-server and remote-ssh extension for vscode.
@baseline0 @zacps Please could you enable logging as follows:
Jupyter->Logging
verbose
Jupyter
output panel.This message indicates that python
is not in PATH
I'd like the logs to see what Python is used.
08:51:51.019 [error] Kernel died Error: spawn python ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:286:19)
at onErrorNT (node:internal/child_process:484:16)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn python',
path: 'python',
spawnargs: [
'-m',
'ipykernel_launcher',
'--f=/home/~/.local/share/jupyter/runtime/kernel-v2-2311178cDwjhvlbJF.json'
]
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Applies To
What happened?
Created a new notebook, and attempted to select a kernel and run a cell.
The kernel picker shows no options under Python environments, and running a cell shows:
This broke suddenly, without any obvious changes on my part (as far as I know).
VS Code Version
Version: 1.90.2 Commit: 5437499feb04f7a586f677b155b039bc2b3669eb Date: 2024-06-18T22:33:48.698Z Electron: 29.4.0 ElectronBuildId: 9728852 Chromium: 122.0.6261.156 Node.js: 20.9.0 V8: 12.2.281.27-electron.0 OS: Linux x64 6.5.0-41-generic snap
Jupyter Extension Version
v2024.5.0
Jupyter logs
Coding Language and Runtime Version
Python 3.10.12
Language Extension Version (if applicable)
v2024.8.1
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local