Boot jupyter from within specific conda environment Boot from outside vs.conda environment

jupyter (notebook or lab) can be used without any problems by launching specific conda environments.
condaIf you boot from outside your environment, you will receive the following error when selecting your kernel:
(jupyter I don't really understand the behavior around me... I've looked into it a lot, but I'm struggling.)

What can we infer is the cause of this phenomenon?
I would like to ask for your help.

.
.
  File "C:\Users\shinji\anaconda3\envs\my_env\lib\site-packages\zmq\backend\cython\_init__.py", line 6, in <module>
    from.import(constants, error, message, context,
ImportError: DLL load failed: The specified module could not be found

Launching from within a specific condaenvironment

At the command prompt,

 C:\Users\shinji\dir>activate my_env
(my_env) C:\Users\shinji\dir>jupyter lab

After starting the jupyter lab,
Select kernel:my_env

condaBoot outside your environment

At the command prompt,

 C:\Users\shinji\dir>jupyter lab

After starting the jupyter lab,
Select kernel:my_env

By the way, use a normal command prompt instead of Anaconda Prompt.
The operating system is Windows 10.

python anaconda jupyter-notebook conda jupyter-lab

2022-09-30 21:51

1 Answers

It may have already been resolved, but I have solved a similar problem with the addition of PATH, so I will write it down.
The symptom is
·Jupyter notebook can be launched from anaconda prompt.
·When I try to launch jupyter notebook from another environment (in my case, git bash), I get an opening error.
The response is
·Add the following to the PATH of the environment variable, where xxx is the path to anaconda.
xxx\Anaconda3; xxx\Anaconda3\library\mingw-w64\bin; xxx\Anaconda3\library\usr\bin; xxx\Anaconda3\library\bin; xxx\Anaconda3\scripts; xxx\Anaconda3\bin; xxx\Anaconda3\condabin;
As a result
·You can launch the jupyter notebook in other environments (in your case, git bash).
Background to this response
·Checked how the anaconda prompt is started.
%windir%\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy ByPass-NoExit-Command"&'xxx\Anaconda3\shell\condabin\conda-hook.ps1';conda activate'xxx\Anaconda3'"
·Check conda-hook.ps1 and call it Conda.psm1
Added path in Add-Sys-Prefix-To-Path().
There seems to have been other processing done, but I haven't been able to confirm it in detail.

Check "Through PATH" because it was set to the default setting during anaconda installation. I think it's because it wasn't included.

2022-09-30 21:51

If you have any answers or tips

Popular Tags

python x 4647
android x 1593
java x 1494
javascript x 1427
c x 927
c++ x 878
ruby-on-rails x 696
php x 692
python3 x 685
html x 656

Popular Questions

849 Uncaught (inpromise) Error on Electron: An object could not be cloned
1232 When building Fast API+Uvicorn environment with PyInstaller, console=False results in an error
769 M2 Mac fails to install rbenv install 3.1.3 due to errors
768 GDB gets version error when attempting to debug with the Presense SDK (IDE)
1069 In Java servlet, when SHA-256 sends WW-Authenticate header for digest authentication, the client does not return the result.