You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment while getting started on a project I'm finding I'm frequently missing a package I wish I had installed.
I have built up lots of state in jupyter and don't want to kill my kernel (or I have some very long running jobs I want to leave running).
How do I add something to my kernel.python.*.extraPackages and rebuild the environment, but keep my kernel? Is such a thing possible, or am I forced to quit the kernel and come back in? In the "pre nix" world I would pip instal something and then immediately import it but I'm guessing I can't quite do that here.
The text was updated successfully, but these errors were encountered:
Hey @pwaller
I don't think such a thing is possible. When the kernel is created, it is given a unique path in the Nix store. When a package is add/removed/modified, a new path is created. This is necessary for reproducibility.
if you want I can add an option of impure in the module to enable the mutable environment. I used to enable that option to debug a kernel or source of the kernel.
At the moment while getting started on a project I'm finding I'm frequently missing a package I wish I had installed.
I have built up lots of state in jupyter and don't want to kill my kernel (or I have some very long running jobs I want to leave running).
How do I add something to my
kernel.python.*.extraPackages
and rebuild the environment, but keep my kernel? Is such a thing possible, or am I forced to quit the kernel and come back in? In the "pre nix" world I would pip instal something and then immediately import it but I'm guessing I can't quite do that here.The text was updated successfully, but these errors were encountered: