nbconvert can sometimes not be found, we should install it next to the extension like ipykernel

[rchiodo]

No description provided.

[DonJayamanne]

Some implications

• For every python environment (different python versions), we'd end up installing nbconvert.
• nbconvert is similar to jupyter, & its agnostic of the kernel & unrelated. Its basically a tool that can be used for all notebooks & all kernels. Hence I don't think we sholuld install this every time.

I still think we should install this into one place, the jupyter interpreter (single place for all tools that will work across all notebooks/kernels & python versions).

IpyKernel is slightly different. This must be installed in each kernel, where as with nbconvert, its not a must.

[DonJayamanne]

nbconvert can sometimes not be found

Do we know when this cannot be found, i think we shoudl try to get to the bottom of that.

[rchiodo]

User didn't install full jupyter is the most obvious scenario.

[DonJayamanne]

User didn't install full jupyter is the most obvious scenario.

Can't we solve this by then checking if jupyter is also installed when checking for nbconvert?

[rchiodo]

You can have jupyter without nbconvert.

[DonJayamanne]

Yes. WHat i'm suggesting is when users install nbconvert, we also install jupyter into this single interpreter which is the jupyter interepreter.
I.e. a way to solve User didn't install full jupyter is the most obvious scenario.

[DonJayamanne]

Oh wait I see a problem, which maybe what you're trying to hightlight.
Raw kernel users won't have a designated jupyter interpreter. Hence when users attempt to use nbconvert, then this doesn't necessarily get installed into a single location, like we do with Jupyter.

Wouldn't using a single interpreter for such tools solve the problem. I.e. use a single python intererpetrt (we call this jupyter interpreter), for all tools like nbconvert, jupyter, etc.

[DonJayamanne]

There haven't been any upvotes nor complaints in this space, hence closing this issue