Failed to find a compatible python environment at the configured path (3.3.2-2+)
See original GitHub issueDescription
With the latest release (v3.3.2-2) of Jupyterlab Desktop, I can’t use python env created by conda. It prompted with the following message. With v3.3.2-1, I didn’t have any issue.
failed to find a compatible python environment at the configured path “/users/p.xing/library/jupyterlab-desktop/jlab_server/bin/python”. environment python package requirements are: jupyterlab >=3.1.0.
Reproduce
- Install the latest v3.3.2-2
- activate python env with
conda activate jupyterlab
- get python dir
which python
- Use the prompted path
/Users/myUserName/miniconda3/envs/jupyterlab/bin/python
as the Jupyter lab desktop custom env path - failed to boot
Expected behavior
(pre) Solution
Using the v3.3.2-1 pkg installer, boot up with no issue.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:37 (12 by maintainers)
Top Results From Across the Web
Failed to find a compatible Python environment at the ...
I select Use a custom Python environment, click Select Python path and choose the path to the Python 3.10 (e.g. ~\AppData\Local\Programs\Python\ ...
Read more >Jupyter Desktop Set Python Environment Error Message
Jupyter Desktop Set Python Environment Error Message ... I'm going to try to fix it my way, and get a Python 3.10 kernel...
Read more >JupyterLab Windows desktop version cannot run error ...
JupyterLab desktop Windows version cannot run. When I open the software and it raises an error: jupyterlab_app Environment not found ...
Read more >PEP 405 – Python Virtual Environments
This PEP proposes to add to Python a mechanism for lightweight “virtual environments” with their own site directories, optionally isolated from system site ......
Read more >pipenv Documentation - Read the Docs
Pipenv is a tool that aims to bring the best of all packaging worlds (bundler, composer, npm, cargo, yarn, etc.) to the. Python...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can also confirm that this is similarly broken on M1 Pro. It is impossible to switch environments from conda to pip. The system never recognizes my virtualenv with jupyterlab installed. It works just fine on my Intel Mac Mini.
I cannot use Jupyter Desktop at all since Conda is a nonviable environment for us.
Jupyter installed via homebrew, using the instructions above, works.
Hi. I upgraded from
jupyterlab-app (3.1.12-1)
tojupyterlab-desktop (3.3.4-2)
on my Debian Linux laptop and got this error too.I ran
mv ~/.config/jupyterlab_app{,.bak}
after removingjupyterlab-app (3.1.12-1)
. I am trying to use a conda env Python3 too.conda
is alreay in myPATH
, which can be confirmed by runningconda activate sklearn-env
to get a working python 3.9.13 env.I tried launching in a terminal with
/opt/JupyterLab/jupyterlab-desktop
command after I activated the conda Python3 env but the same error persisted. This is~/.config/jupyterlab-desktop/logs/main.log
:See the line
It’s definitely looking for the wrong thing, where I was told to choose a the path to python (in my case
/home/adam/Programs/miniconda3/envs/sklearn-env/bin/python3
), but it’s somehow looking for a env? I may have to set/home/adam/Programs/miniconda3/envs/
atUse a custom Python environment
but it won’t let me choose a path to a dir. Help this helps.