You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to see if I can automate the testing of .ipynb notebooks after they are served using jupyter-lite. The problem is given a python notebook, the script should output whether the execution completed successfully or not. When I installed using
pip install jupyterlite-pyodide-kernel
I can't see the kernel in the kernel list:
% jupyter kernelspec list
Available kernels:
python3 /Users/kpl/mambaforge/envs/qe/share/jupyter/kernels/python3
xpython-raw /Users/kpl/mambaforge/envs/qe/share/jupyter/kernels/xpython-raw
How do I test the notebooks or how do I fix the installation to see this in kernel list.
The text was updated successfully, but these errors were encountered:
A workaround, for now, could be in this form (if you use the Pyodide kernel):
# convert the notebook to a Python file
python -m pip install jupytext
python -m jupytext --to py your_notebook.ipynb # or py:percent if you like# install Pyodide and activate
python -m pip install pyodide-build
pyodide xbuildenv install 0.27.0 # or your preferred Pyodide version
pyodide venv .venv-pyodide
source .venv-pyodide/bin/activate
# run the notebook as a Python file
python my_notebook.py
As a more robust solution, maybe it can be possible to run the notebook as one usually does – it would require making the Pyodide/Xeus kernels visible in the kernel list and making it possible for notebook testing tools like papermill or nbmake to connect to them.
I am trying to see if I can automate the testing of
.ipynb
notebooks after they are served using jupyter-lite. The problem is given a python notebook, the script should output whether the execution completed successfully or not. When I installed usingI can't see the kernel in the kernel list:
How do I test the notebooks or how do I fix the installation to see this in kernel list.
The text was updated successfully, but these errors were encountered: