Skip to main content

FAQ

If you did not find a way to use your Python package in Notebook.link, please make sure that it's either:

  • a pure Python package provided as a Python wheel on PyPi: then you can install it with pip
  • published on conda-forge as a noarch package
  • compiled for WASM and published on emscripten-forge
danger

Notebook.link does not support Python packages published as tarballs .tar.gz or compiled packages from PyPi, since those are not compiled for WASM. The package needs to either be a pure Python library from PyPi or conda-forge or compiled for WASM and published on emscripten-forge.

Can I use the Pyodide JupyterLite kernel?​

You can easily install the pyodide kernel in Notebook.link using the following environment:

name: pyodide-environment
channels:
  - conda-forge
dependencies:
  - jupyterlite-pyodide-kernel
warning

The Pyodide kernel has its own package distribution logic, its Python runtime does not know about the rest of the environment. e.g. installing packages like ipyleaflet alongside pyodide will not make ipyleaflet importable there.

In my environment definition, do the order of channels matter?​

Yes! The order of channels in the environment definition matters.

Notebook.link uses strict channel priority, meaning that if conda-forge is before emscripten-forge in the list of channels, packages from conda-forge will take precedence and you may have solving issues. Please make sure to put the emscripten-forge channel first.