Open yuvipanda opened 1 year ago
I built it with (the equivalent of) jupyter lite build --contents <path>
and there seems to be no effect here.
@jtpio and @bollwyvl would love to hear what I might be doing wrong :)
you have logs, or a broken site, or a version you tested with, or something? It could be the schema needs to change, if the upstream config has changed without us noticing, as we don't exercise that in our heavy duty site... but probably could with echo-kernel
or something.
@yuvipanda the location of jupyter-lite.json
is also relevant, maybe it ends up in the wrong directory and is not picked up.
I wrote this up on how to disable specific kernels, but it doesn't seem to work?
By default, 3 kernels are made available in all JupyterLites built with this action:
This might be quite confusing to your end users, as the two python kernels also have different behavior!
Pyodide doesn't have a way to pre-install packages (until []() is merged), while XPython doesn't support installing packages at runtime with
micropip
. While eventually they might all converge, for now, as the author of the GitHub repo, you need to make this choice for your users.You can disable some kernels by creating a file named
jupyter-lite.json
with the following contents: