exodide: build_ext for Pyodide
1. Overview
Pyodide is a WebAssembly variant of CPython. By using it, we can run Python code inside web browser.
Although we can run most of pure-Python packages on Pyodide, however, available C/C++ extension packages are limited to builtin packages. (Update: From v0.21.0, Pyodide started to accept non-builtin C/C++ packages.)
The motivation of this project (exodide) is providing C/C++ extension builder for Pyodide, and enables users to run your own custom C/C++ extension packages on Pyodide.
2. Usage
2.1 Requirement Summary
- 2.3: Build
- Emscripten v3.1.14
- wheel
- C/C++ package source working on CPython 3.10.2
- 2.4: Run
- Pyodide v0.21.0
- 2.5: Inspect
2.2 Install exodide
2.2.1 Install from PyPI
You can install exodide from PyPI
pip install exodidepip install exodide[build]- With build dependencies
pip install exodide[inspect]- With inspect dependencies
pip install exodide[all]- With all dependencies
2.2.2 Use docker image
We provide docker image
docker run -it -v <your package source path>:/src ghcr.io/ymd-h/exodide:latest bash
# Inside docker container
source /emsdk/emsdk_env.sh # Set PATH for emcc/em++
2.2.3 Install from Source
Since this repository doesn't contains patched headers, you cannot
install directly from GitHub like pip install git+https://github.com/ymd-h/exodide.
git clone --recursive --depth 1 https://github.com/ymd-h/exodide.git
cd exodide
make
pip install .
2.3 Build with exodide
The followings are reuired;
- Emscripten v3.1.14
- Set up
emccandem++as the official document
- Set up
- C/C++ extension package source working on Python 3.10
wheel(pip install exodide[build]install it, too.)
2.3.1 Method 1: Main Usage
from setuptools import setup
from exodide import build
# omit
setup(
# omit
cmdclass=build.cmdclass(), # {'build': build.build, 'build_ext': build.build_ext}
)
then CC=emcc CXX=em++ python setup.py bdist_wheel.
2.3.2 Method 2: Fine tuning for Power User
If your package has special build flow, you might need to call exodide internal API.
All internal build API are implemented at exodide.build module.
system_include() -> str: System include directory of host Pythonexodide_include() -> List[str]: Include directories inside exodide package.adjust_include(include: List[str]) -> List[str]: Adjust include directories- Internally
system_include()andexodide_include()are used
- Internally
exodide_links() -> List[str]: Linker argumentsexodide_unsupported_links() -> List[str]: Unsupported linker argumentsexodide_platform_tag() -> str: Platform name tag for wheel
2.3.3 Method 3: Quick Usage
We also provide custom setup command exodide_wheel.
The following command have same effect with the first option at '2.3.1 Main Usage'.
CC=emcc CXX=em++ python setup.py --command-packages exodide exodide_wheel
2.3.4 Notes
Pyodide doesn't provide all the functionalities of CPython, so that
you might need to modify your package. You can detect Emscripten
compiler by __EMSCRIPTEN__ macro (ref).
#ifdef __EMSCRIPTEN__
// Code for Pyodide
#else
// Code for Others
#endif
2.4 Install extension package to Pyodide
Note Since from Pyodide v0.21.0
micropip.install()accepts custom URL,exodide.installmodule become deprecated.
Pyodide v0.21 is required.
const pyodide = await loadPyodide();
await pyodide.runPythonAsync(`
import micropip
micropip.install("example.com/your-package-X.Y.Z-cp310-cp310-emscripten_3_1_14_wasm32.whl")
import your_package
# omit
`);
2.5 Inspect Shared Object (for Debugging)
Fot inspect, numpy is also required, and you can install with
pip install exodide[inspect].
python3 -m exodide.inspect your-package/your-module.so
Currently, exodide.inspect module prints dylink / dylink.0
custom section, which are used for metadata of Wasm dynamic link.
3. LICENSEs
We utilize other projects and these codes obey their original lisences. We distribute patched header files of CPython and NumPy, too.
- CPython: https://www.python.org/
cpythondirectory- PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
- NumPy: https://numpy.org/
numpydirectory andscript/code_generatorsdirectory- BSD 3-Clause
- Pyodide: https://pyodide.org/en/stable/
pyodidedirectory- MPL-2.0
- Others (exodide original codes)
4. Technical Details
Technical details are described here
Metadata
Release files for exodide 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| exodide-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for exodide-1.0.4-py3-none-any.whl |
Release files / exodide-1.0.4-py3-none-any.whl
| Download URL | exodide-1.0.4-py3-none-any.whl |
|---|---|
| Size | 351.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b49aa89811499f49a792ccc7be2ed512f6dfe5e61fee93373539d167da4260e8
|
|
BLAKE2b-256 checksum How to use checksums |
47ea9a3dd778204f947e561404237c8460a9da406e529cb7c6fcdf0a2a079356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for exodide 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.