I am a co-maintainer of the Spack package manager (https://spack.io) and we would like to ship more Jupyter extensions, such as ipympl in Spack.
From looking at the structure in other package managers such as Conda, we see that Jupyter extensions usually need to be installed into a common prefix, e.g.,
Spack splits packages by default into their own prefixes, which allows to mix-and-match compatible packages for virtual environments via environment variables. Thus, is it possible to hint Jupyter to more than one prefix when looking for extensions? We would ideally like to set an environment variable similar to
NB_EXTENSION_PATH, which hints a list of (additional) prefix roots to check for additional packages.
Is that already possible or something to consider as an extended configuration option?