> How can I debug what's wrong and particularly is there a way to start that particular kernel, based on those kernel spec alone?
Normally those 'restarting kernel' messages come with a traceback saying what went wrong. I'm not sure why they don't in your case.
You can run a kernel through Jupyter by running 'jupyter kernel --kernel your-kernel-name' (where your-kernel-name is whatever you called the folder with kernel.json in). Alternatively, you can set the environment variables in your shell, join up argv with spaces, and run that in the shell.
On Fri, 15 Feb 2019 at 23:10, Alessandro Dentella <[hidden email]> wrote:
I'd like to bettere understand "argv" list. It's the arguments passed
to what exactely? -m and --ext are for python/ipython, who interprets -f?
I have a django project whit a std virtualenv with a working kernel
defined as follows: