-
Notifications
You must be signed in to change notification settings - Fork 334
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
How to specify the conda environment in which hydrogen (jupyter) starts? #899
Comments
Guessing from #501 this should do the job: source activate thisenv
python -m ipykernel install --user --name thisenv |
It may also work if you start Atom from the command line after running |
Thank you. But where do I put this? It doesn't match the JSON which seems to be required for Kernel specs |
As long as you have jupyter installed you don't need to manually add kernelspecs inside the Hydrogen settings, we automatically detect installed kernels. You can savely remove any JSON you added to the Hydrogen kernel specs settings. You can run "Hydrogen: Update Kernels" or restart Atom for the changes to take effect. Next time you want to run Python code you'll be prompted to select the environment you just created. |
One thing to add: You'll only need to run source activate thisenv
python -m ipykernel install --user --name thisenv once in the command line. |
thank you very much! all works. |
Awesome |
I'm terribly sorry. Turns out I haven't installed ipykernel yet. 'pip install ipykernel' solves the problem and for anyone using anaconda with tensorflow in a separate env and just couldn't live without atom + hydrogen, be sure to check the above wonderful solution by @lgeiger Thx for the answer but the second line wouldn't work, it says No module named ipykernel
|
I have tried working from #501 but can't make any progress.
I have Hydrogen 1.18.0 and want to be able to specify the conda environment that in which I launch my jupyter notebook.
From the command line, I'd do
How do I achieve the same thing from Hydrogen?
Many thanks
The text was updated successfully, but these errors were encountered: