nb_conda_kernels and jupyter notebook extensions

When using extensions, dependencies (to my knowledge) have to be installed into each kernel environment separately.

A typical example would be the jupyter extension Autopep8 requries the package autopep8. Currently I have to install autopep8 in every kernel environment.

Is there a way to only install such extension dependencies to the actual notebook enviornment and not to every kernel environment I want to use in a notebook?

[fcollonval]

The discussion is getting quite of topic.

To sum-up, the requirement of autopep8 on each environment is a consequence of the implementation in jupyter-autopep8. @skwde you could open a request on that repository to use the library installed in the server environment rather than in the kernel environment.

If you need to share packages between environment, I suggest (but this can be dangerous) to make use of PYTHONPATH.

A small comment, I don’t know the rational behind the need of autopep8 requirement to be in the kernel environment. But I can image it has to do with supporting various versions of Python.

[skwde]

@tbsexton I agree that environment.yml are great to keep track of environments and also share them.

However I still don’t think that packages, installed because they are jupyter extension dependencies such as autopep8, should be in the ipykernel environment. They should stay with the extension. Otherwise it simply leads to duplicated installes.

Also your point regarding interoperability does not realy hold in my opinion. Just image the person I am sharing the enviornment with doesn’t use the same jupyter extensions. Worse still, if the person doesn’t even use jupyter than he gets an environment with not only ipykernel as a useless package but also numerous others.