Can we run it against colab kernel? #9753
-
I wanted to replicate exact versions of packages listed in one of the project's Pipfile inside google colab. Since google colab does not allow to do so, I tried to somewhat convoluted way. I started vscode server inside colab and accessed it using ngrok using ColabCode. The code is in this notebook. With this code running I was able to run vscode in browser. Now from in-browser vscode's terminal:
(If this works, it will allow me have vscode's debugging capability, jupyter's visualization capability, colab's GPUs all running against replicable environment captured by Pipfile) Update If I change the python interpreter of notebook to default one instead of pipenv (at the top right corner of notebook), the notebook works. So it seems to fail to work only for pipenv. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Looks to me like the jupyter config on the VM is requesting google specific stuff. This message here:
That's likely because the config for the jupyter server on the box specifies kernels are based on google colab kernels. However you're starting your kernel without any google stuff in the path. You might try deleting the jupyter_notebook_config.py on the machine (if that's findable). It's the thing that's likely specifying the base class for a kernel. |
Beta Was this translation helpful? Give feedback.
Looks to me like the jupyter config on the VM is requesting google specific stuff.
This message here:
That's likely because the config for the jupyter server on the box specifies kernels are based on google colab kernels. However you're starting your kernel without any google stuff in the path.
You might try deleting the jupyter_notebook_config.py on the machine (if that's findable). It's the thing that's likely specifying the base class for a kernel.