Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
jupyterlite-pyodide-kernel
Advanced tools
A Python kernel for JupyterLite powered by Pyodide,
python >=3.8
status | jupyterlite-pyodide-kernel | jupyterlite-core | jupyterlab | notebook | retrolab |
---|---|---|---|---|---|
pre | 0.4.* | >=0.4,<0.5 | >=4.2.0,<4.3 | >=7.2.0,<7.3 | - |
stable | 0.3.* | >=0.3,<0.4 | >=4.1.1,<4.2 | >=7.1.0,<7.2 | - |
stable | 0.2.* | >=0.2,<0.3 | >=4.0.7,<4.1 | >=7.0.5,<8 | - |
stable | 0.1.* | >=0.1,<0.2 | >=3.5,<3.6 | - | >=0.3,<0.4 |
Installing the matching version of JupyterLab with your package manager can help ensure
matching labextension assets and kernel dependencies, even though this kernel does not
yet work in a full, jupyter_server
-hosted client such as JupyterLab or Notebook.
jupyterlite-pyodide-kernel | pyodide | python | emscripten |
---|---|---|---|
>=0.1.0,<=0.1.1 | 0.23.* | 3.10.* | 3.1.29 |
>=0.1.2,<=0.2.1 | 0.24.* | 3.10.* | 3.1.45 |
>=0.2.2,<=0.2.3 | 0.25.* | 3.11.* | 3.1.46 |
>=0.3.*,<=0.4.0 | 0.25.* | 3.11.* | 3.1.46 |
>=0.4.*,<=0.5.0 | 0.26.* | 3.12.* | 3.1.58 |
Note that the Emscripten version is strict down to the bugfix version.
To install the Pyodide kernel labextension and the CLI addons for jupyter lite
, run:
pip install jupyterlite-pyodide-kernel
or with conda
, mamba
, micromamba
, etc.
conda install -c conda-forge jupyterlite-pyodide-kernel
For more options see the development install or contributing guide.
Build a JupyterLite site:
jupyter lite build
Some new CLI options are also available:
jupyter lite --help
This should show something like this:
--piplite-wheels=<typedtuple-item-1>...
Local paths or URLs of piplite-compatible wheels to copy and index
Default: ()
Equivalent to: [--PipliteAddon.piplite_urls]
--pyodide=<Unicode>
Local path or URL of a pyodide distribution tarball
Default: ''
Equivalent to: [--PyodideAddon.pyodide_url]
⚠️ The documentation for advanced configuration is available from the main JupyterLite documentation site:
To remove the extension, run:
pip uninstall jupyterlite-pyodide-kernel # or however you installed it
To install pre-release versions with pip
:
pip install --upgrade --pre jupyterlite-pyodide-kernel
Or, similarly for the conda
ecosystem, for alpha
packages:
conda install \
-c conda-forge/label/jupyterlite_core_alpha \
-c conda-forge/label/jupyterlite_pyodide_kernel_alpha \
-c conda-forge \
jupyterlite-pyodide-kernel
Note:
_beta
and_rc
packages would follow a similar channel naming convention
Below is an short overview of getting up and running quickly. Please see the contributing guide for full details.
Recommended a Python virtual environment provided by a tool of choice, e.g. one of:
virtualenv
mamba
conda
Ensure the local development environment has:
git
nodejs 20
python >=3.8
git clone https://github.com/jupyterlite/pyodide-kernel
cd pyodide-kernel
npm run quickstart
Then, serve the built demo site, documentation, and test reports with Python's built-in HTTP server:
jlpm serve
FAQs
Python kernel for JupyterLite powered by Pyodide
We found that jupyterlite-pyodide-kernel demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.