Jupyter exhibits surprising behavior in virtualenv due to non-containered files

[xkortex]

On more than one occasion, I have experienced somewhat surprising issues and bugs (only raised the most recent issue because I just figured it out) due to what I ultimately determined to be the way Jupyter handles config files by default. Normally, the config file lives in ${HOME}/.config, irrespective of running pip install jupyter inside of a VE. There is a way to set environment variables to specify a custom path, but there are no hooks or flags that I am currently aware of such that this occurs upon a Jupyter install from a VE. Since VE provides isolation, initially I (naively) assumed Jupyter installs in different VEs would have no way of interfering with each other.

More curiously, it appears that some configs exist in VE/share/jupyter/nbextensions. But I also have ${HOME}/.config/jupyter/nbextensions which to be honest I'm not sure where it came from, as I have done all python work from within VEs (no global or pip --user installs). However, I notice on a fresh userspace, with a minimal VE with only Jupyter, Ipywidgets, and Ipyvolume installed, there is no jupyter in .config. Some other pip install must have put it there.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.