Michael Aye

No, my fully setup conda env shows the same errors, and I don't have any other jupyter probs there?

i get indeed the same error: ```python In [1]: from jupyter_client.manager import start_new_kernel In [2]: start_new_kernel(extra_arguments=['--matplotlib=inline']) /Users/klay6683/miniconda3/bin/python: Error while finding spec for 'IPython.kernel' (ImportError: No module named 'IPython') --------------------------------------------------------------------------- RuntimeError...

wow, some stone-age settings that I don't use since long, as I'm using nb_conda_kernels for managing those... ```bash (stable) └─❱❱❱ jupyter kernelspec list +7371 14:34 ❰─┘ Available kernels: python2 /Users/klay6683/Library/Jupyter/kernels/python2...

However: both kernels point actually to working conda envs ( because i always use the same envs names). The python3 one points to conda root though.

yep, both the start_new_kernel and the nbval test now go through. Thanks! But what happened though? The path to the python3 kernel was correct, was there maybe an old setting...

The latter, as I don't have a full env in conda root, only using it for package management. Thanks for your debugging help!

oh, that's because my prompt (zsh->garrett) includes git status information, and the status is defined by git getting active, using the nbstripout filter to define the status for each notebook.

are u aware that git apparently is able to cache the status somehow? It's only slow for me for the first time entering the folder after I-dont-know-what-interval-or-action. After that it's...

ssd.

sorry, I don't know what the `--current-env` is or what it is supposed to do. I scanned your docs but it isn't mentioned? I made sure that the notebook was...