Describe the bug
Installing jupyterlab from the esri conda channel on Linux creates a broken Jupyter kernel whose kernel.json incorrectly references a Windows executable (python.exe) and uses a Windows-style backslash path.
This causes JupyterLab to fail to start any kernel, producing a “No such file or directory … python.exe” error.
The issue appears to be caused by distributing a Windows‑specific kernel spec even when installed on Linux.
To Reproduce
Steps to reproduce the behavior:
conda create -n fail
conda activate fail
conda install -c esri jupyterlab
jupyter kernelspec list
Inspect the kernel:
cat $CONDA_PREFIX/share/jupyter/kernels/python3/kernel.json
{
"argv": [
".../envs/fail\\python.exe",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
],
"display_name": "Python 3 (ipykernel)",
"language": "python"
}
Expected behavior
The jupyter kernel should just work on Linux.
"argv": [
".../envs/fail/bin/python",
"-m",
"ipykernel_launcher",
"-f",
"{connection_file}"
]
Platform (please complete the following information):
- OS: Linux (Debian/Ubuntu-based; same behavior under WSL2 and native Linux)
- Browser not relevant
- Python API Version
2.4.3
Describe the bug
Installing
jupyterlabfrom theesriconda channel on Linux creates a broken Jupyter kernel whosekernel.jsonincorrectly references a Windows executable (python.exe) and uses a Windows-style backslash path.This causes JupyterLab to fail to start any kernel, producing a “No such file or directory … python.exe” error.
The issue appears to be caused by distributing a Windows‑specific kernel spec even when installed on Linux.
To Reproduce
Steps to reproduce the behavior:
Inspect the kernel:
Expected behavior
The jupyter kernel should just work on Linux.
Platform (please complete the following information):
2.4.3