Closed rtbs-dev closed 1 year ago
Theoretically, coconut --jupyter
should do approximately this. Let me know if that works for you or if you are still having any issues.
I guess the one thing coconut --jupyter
doesn't support currently is --user
installation. Perhaps coconut --jupyter --user
or coconut --jupyter install --user
should be supported for that.
In addition to the already-supported coconut --jupyter
command, coconut --jupyter install
and coconut --jupyter install --user
should now be supported on coconut-develop>=3.0.2-post_dev14
(pip uninstall coconut
and pip install -U coconut-develop
).
Oh phenomenal! I didn't realize the coconut --jupyter command was available if only coconut[kernel] was installed, or that it would automatically recognize the correct pyenv. But imo I really like the coconut --jupyter install syntax! Thanks again!
Hi there! I've moved away from
nb_conda_kernels
due to... so many conflicting dependencies and CI/CD nightmares. But thepip install coconut[kernel]
technique still works great for this workflow, which makes use ofpyenv
/virtualenv
. Jupyter/lab can find the kernel just fine, provided a smallkernel.json
config file. I figured out how to add it in a way that duplicates those workflows.Proposal
Request: add a
coconut kernel install [--name] [--user]
cli commandfunctionality: creates a
~/.local/share/jupyter/kernels/{myenv}-coconut/kernel.json
spec file, with the contents:Where the
{PYENV_ROOT}
and{myenv}
variables get replaced with the pyenv root dir and currently-activate environment name, respectively.For now I just copy+edit that file around to new kernel folders every time I make one that uses Coconut, but that would be easier if there was a coconut equivalent to the
python -m ipykernel install --user --name {myenv}
command that I run for python kernels that makes the kernel.json automatically.Assumptions: The user wants a coconut kernel to have the same name as the python environment it's originating from, but with an added
-coconut
in the name. Seemed good enough?