This release is a pre-release and may not be stable for production use.
libigl Python Bindings
This repository contains the source code for the python bindings for the C++ libigl library written using nanobind. Functions allow NumPy arrays as input and output for dense matrices and vectors and SciPy sparse matrices for sparse matrices.
Installation
python -m pip install libigl
Pyodide (WebAssembly)
Wheels for Pyodide 314.0 (Python 3.14, wasm32) are built and tested alongside
the native wheels. In Pyodide, install the development release with:
import micropip
await micropip.install("libigl", pre=True)
import igl
These wheels include igl.embree, igl.copyleft.cgal, and type stubs for all
modules. Geometry processing runs without worker threads. CGAL uses Boost
exact arithmetic and its round-to-nearest interval implementation; Embree uses
WebAssembly SIMD. Stubs are generated from the compiled modules inside Pyodide
before the wheel is tested and published.
Documentation
| ⚠️ WARNING |
|---|
| The python-binding documentation is perennially out of date and will likely be removed/changed. |
Getting the current version of libigl within python code
Since version 2.5.4.dev0, the igl.__version__ attribute has been removed. To
get the version of the libigl package you're using within your python code, you
can use the following code:
import importlib.metadata
libigl_version = importlib.metadata.version('libigl')
The version of libigl is defined in the pyproject.toml file.
Compiling and modifying the bindings
According to the scikit-build-core documentation, the way to make an editable (incremental) build is to:
- Preinstall the dependencies (at the top of pyproject.toml
- Then use this very long command:
CMAKE_BUILD_PARALLEL_LEVEL=10 python -m pip install --no-build-isolation --config-settings=editable.rebuild=true -Cbuild-dir=build -ve.
The CMAKE_BUILD_PARALLEL_LEVEL=10 will invoke with 10 parallel build threads.
Adding a missing binding
Bindings are fairly mechanical to write. For example, suppose we didn't have a
binding for the c++ function igl::moments. The first step would be to look at
the corresponding .h header file in the C++ libigl library:
moments.h.
Then we would create the src/moments.cpp file in this project
which uses Eigen::MatrixXN for numeric types and Eigen::MatrixXI for integer
types. Typically this requires a simple wrapper around the function matching
its signature to these types and some boilerplate void bind_moments(... code which adds the function to the python module.
Simply adding this .cpp file will be enough to add the bindings on the next
build.
If submitting a pull request with a new binding, please also add an execution
test in tests/test_all.py to ensure the binding can at least be called as
expected.
Packaging a wheel from an existing build
If you already have a compiled build directory, you can package it into a
.whl without recompiling and install that wheel into other virtual
environments on the same machine:
python -m pip wheel --no-build-isolation --no-deps -Cbuild-dir=build -w wheelhouse .
pip install wheelhouse/libigl-*.whl
The --no-deps flag skips bundling numpy/scipy (the target environment must
have them already). No compiler or CMake is required in the target environment.
Testing cibuildwheel locally
To build and test the Pyodide wheel on Linux or macOS, use Python 3.14 and Node.js 24:
python -m pip install cibuildwheel==4.3.5
python -m cibuildwheel --platform pyodide --output-dir wheelhouse
Install whichever version of Python from the official website and then run:
/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 -m venv venv-official-3.11
source venv-official-3.11/bin/activate
python -m pip install cibuildwheel
CIBW_BUILD="cp311-*" python -m cibuildwheel --output-dir wheelhouse --platform macos
Downloading all the artifacts
A successful .github/workflows/wheels.yml run will a lot of .whl files. To download these all at once, you can use the following command:
mkdir wheelhouse
cd wheelhouse
gh run download [runid]
Then these can be uploaded to pypi using:
for f in wheelhouse/*/*.whl wheelhouse/*/*.tar.gz; do
python3 -m twine upload --repository pypi "$f" || echo "Skipping failed upload: $f"
done
Acknowledgements
The original python bindings were generated and maintained by @teseoch, @KarlLeell, @fwilliams, @skoch9, and @danielepanozzo
The modern python bindings (since 2.5.4.dev0) can largely be blamed on @alecjacobson.
1 maintainer
Metadata
1 maintainer
Release files for libigl 2.6.4.dev3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| libigl-2.6.4.dev3.tar.gz | 41.3 MB | With provenance | Details for libigl-2.6.4.dev3.tar.gz |
Built distributions (wheels)
Total release size: 400.2 MB
Release files / libigl-2.6.4.dev3.tar.gz
| Download URL | libigl-2.6.4.dev3.tar.gz |
|---|---|
| Size | 41.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70c603a19c956aa23f514cf2bf06ff140b687fe73aba6880e3f4284513d7b85b
|
|
BLAKE2b-256 checksum How to use checksums |
291cfb5e6f41d2ae592835411aa86d80a57da5cf2ddd2e0fd1f49666a0e86d52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp314-cp314-pyemscripten_2026_0_wasm32.whl
| Download URL | libigl-2.6.4.dev3-cp314-cp314-pyemscripten_2026_0_wasm32.whl |
|---|---|
| Size | 9.8 MB |
| Tags | CPython 3.14 PyEmscripten 2026.0+ WebAssembly |
|
SHA-256 checksum How to use checksums |
0dd47ea41bd0bd1d8ac82bae5f538e760758a11ea702258ac4fc6160564a3296
|
|
BLAKE2b-256 checksum How to use checksums |
0309502e43e1029a753874a2251a2b97a3b7731871c134865b89bfe56be5fd45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-win_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-win_arm64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.12 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
96c29a42f60dc9178a75aa6a136c409c03938f82fe98b44accb8af2b0455c26d
|
|
BLAKE2b-256 checksum How to use checksums |
aa84a8c807497fef0673dc2cee98799e37cf9a6377e973f75603498a829ba95d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-win_amd64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 20.3 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
6feb97eefa54cc00040578e7258412a1c2c30af2b1cd9a7973d5df12ff2b312a
|
|
BLAKE2b-256 checksum How to use checksums |
7b298adcb5d3039522fad880761821781ef34ae337fdf24ef356cbf0f9571cb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bf19c87219cfdc5712214eed721488f83330ab260a8cb792373dce2b365c7baa
|
|
BLAKE2b-256 checksum How to use checksums |
0e8d8f018b14bd8d8b16eaefac33d3c9bee61354964c643425aa9258676216bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 13.2 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3f96464c971ffd91ad082a4b6b07d178159c1abfb81c037883f4730397deda63
|
|
BLAKE2b-256 checksum How to use checksums |
d04812cb46385194eda8a1cae80643cfc24392baa065ce56320019fe73a5cd60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 12.2 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9a2a81ebcc211913494fc089e9cc85725467d20e7859a73463bb01bb9630b830
|
|
BLAKE2b-256 checksum How to use checksums |
5112cec52ce8c7cc0f59029950e3133c131ad33667971940305f6e38314518a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp312-abi3-macosx_10_15_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp312-abi3-macosx_10_15_x86_64.whl |
|---|---|
| Size | 13.5 MB |
| Tags | CPython 3.12 abi3 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
a648eedaf268714a6261af799949885099822ab3012f3e07927b9f10ab3fd7ce
|
|
BLAKE2b-256 checksum How to use checksums |
a4b915107036a821cef63316fad1ce7f9234dcce09624ec5d1f06cba9fa6de85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-win_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
5f4c5dcc80020f7b72153ff4a907648d10da4cff5febf38a1e42019f2df9264f
|
|
BLAKE2b-256 checksum How to use checksums |
e36cf6e3a415ca8ae28d313a0207b67e84f41afa168c204cc24063d3bee7fe0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-win_amd64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 20.3 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4bd14c9bdeb9abd3c721e5a6f853b3d611c15c84c777442549ea6dfebf18a1d5
|
|
BLAKE2b-256 checksum How to use checksums |
bd93b900626e39cc8f309344d921464897c7afbeda738c967e81d23d6e1627c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
3a68df544f050d9b62678ca9ec26b2da02e9d38b08025b3442e2bf6b5855af2b
|
|
BLAKE2b-256 checksum How to use checksums |
7d8c55adec569e8e1d6e6a84112678c765309ad13241ce2099f8e8585f9f70e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 13.2 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a45d76fb5a98cb0e4604401966a73009b256ddf195942e2acda469070f10aed3
|
|
BLAKE2b-256 checksum How to use checksums |
0c9fa42e0c6878aa2941c281f7883ea18dcee269b4c541a905ec08385bfaaf71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 12.2 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
04c2884daa9d1a8e9c5e57808e0ab47522746e4f8c0a6d4e3074bcc4e7a6775c
|
|
BLAKE2b-256 checksum How to use checksums |
bec8abb00f5710757c7aa8153b8d303dd3ce3d473698c77b6f124fcffa8cf7c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp311-cp311-macosx_10_15_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp311-cp311-macosx_10_15_x86_64.whl |
|---|---|
| Size | 13.5 MB |
| Tags | CPython 3.11 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
1a731186a2b62240ae8df4e93b58f3f3d83aa23907cd18f87ce07bcb3fad9560
|
|
BLAKE2b-256 checksum How to use checksums |
ec743d058693dcc83fef8404953ad2b7bfc20a6ef133c657bb7b2b068ed1ac40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp310-cp310-win_amd64.whl
| Download URL | libigl-2.6.4.dev3-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 20.3 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a11e1d3faea5620dbfdfe9b0e1e4e7fbc8be842a70a7caaebad1ebe6568420ed
|
|
BLAKE2b-256 checksum How to use checksums |
950f66219ab7ad185105967ac8433a20447d5cbe827177eed671bfec211478eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
5230c7024c06c0bbfb36953e42ef97595e5d224b296ac1433867c98d2a8195f9
|
|
BLAKE2b-256 checksum How to use checksums |
72934b54502aee9a70ed1a8d849a0d032fbd62d4c9a74e99b5b42a4e73981251
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | libigl-2.6.4.dev3-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 13.2 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
caa6b9b821f4fd50bc7ca963367de675db0b75d8fc4b4dbd8b51d3c8619eea2f
|
|
BLAKE2b-256 checksum How to use checksums |
9b267a93527385ea09f9d279178444f788f70cc885fe2ca16d0cea1f8a92eb73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 12.2 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ab4741d86b16516a7e9880b566d79d66ed6c61688e7987f151a636bb1529630f
|
|
BLAKE2b-256 checksum How to use checksums |
23de161f806fcafdf8d68755213102bc4177a25ba1003573c85c5899e7f908da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp310-cp310-macosx_10_15_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp310-cp310-macosx_10_15_x86_64.whl |
|---|---|
| Size | 13.5 MB |
| Tags | CPython 3.10 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
661af42e8143a8ef3fee2a37fa8bb8dc0cc303ead6c33bf7e4688adf1a55d627
|
|
BLAKE2b-256 checksum How to use checksums |
a52953a1d68462b19f746fa79108e3707c977f4ee1766b7ac70d1359f806b2fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp39-cp39-win_amd64.whl
| Download URL | libigl-2.6.4.dev3-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 20.3 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0553500e349150cb37655beb7433e3381d1585d195ced9ab5494c4943f065cb5
|
|
BLAKE2b-256 checksum How to use checksums |
f90355b82d2ae9a33980bb2b908f49572844a1a3978598e6e4ad731ac0761a3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0369a55cad5e7d83b50c8065f5ea3765a6be7f6973106f9f74b9627d0960107d
|
|
BLAKE2b-256 checksum How to use checksums |
f84096c5b48fe7eb4881d0c3dedf8296bfe1799cf7a1251f30f2e8e4c08e4b91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | libigl-2.6.4.dev3-cp39-cp39-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 13.2 MB |
| Tags | CPython 3.9 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1570f06f28bc79593ffc89f28a76ca2be52a3415286fe40d6ab79917fd7556e4
|
|
BLAKE2b-256 checksum How to use checksums |
ae5247628732c879afbfe94dfb90d528d02949b246605dca48ffe295f9111c39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp39-cp39-macosx_11_0_arm64.whl
| Download URL | libigl-2.6.4.dev3-cp39-cp39-macosx_11_0_arm64.whl |
|---|---|
| Size | 12.3 MB |
| Tags | CPython 3.9 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
19f677fb8673ebcef4f730986502582dd5c01c6fb76990349aba648101cd8e64
|
|
BLAKE2b-256 checksum How to use checksums |
30f3780b2aaed61ad2aefcae8a9560340a3f6f438bd7dacf70a17b130f8e4e7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp39-cp39-macosx_10_15_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp39-cp39-macosx_10_15_x86_64.whl |
|---|---|
| Size | 13.5 MB |
| Tags | CPython 3.9 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
62b647ae9424b5e99c855422d9f18aac40c297027f6846fa90a210c357f70b56
|
|
BLAKE2b-256 checksum How to use checksums |
51f5ba2b1fcc84754d56af66389bfff2027913671fe04afe9e9fc67fe5e9cf39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp38-cp38-win_amd64.whl
| Download URL | libigl-2.6.4.dev3-cp38-cp38-win_amd64.whl |
|---|---|
| Size | 20.3 MB |
| Tags | CPython 3.8 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
212ae17fed9ebf65411f79c0dad1053ab5cd08c49068150cbe51126859b2aaae
|
|
BLAKE2b-256 checksum How to use checksums |
7b14c3a0dc120a6da1d4025bca430bb8c47c29dac71f5aa6263c145c439e0b8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp38-cp38-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | libigl-2.6.4.dev3-cp38-cp38-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 13.9 MB |
| Tags | CPython 3.8 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
14e50c359ae5f02bfa65f3f87c8e19067d98e8ecf400577c3ddd8f29af993a30
|
|
BLAKE2b-256 checksum How to use checksums |
9f050df9d3d20fed902c0ced7878a2ee3ad135ff6b9930a07d998081115bdb2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / libigl-2.6.4.dev3-cp38-cp38-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | libigl-2.6.4.dev3-cp38-cp38-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 13.2 MB |
| Tags | CPython 3.8 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
b030285551e9de8fd3fccd3af4bfebd8a44aa2d5649facb2b8668f9fd5af607f
|
|
BLAKE2b-256 checksum How to use checksums |
b57e9ae4e1adb0b95c71d953c0ba693a776870f2fc148093f77cdfabae0cfb1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for libigl 2.6.4.dev3
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.
Full provenance
All 27 files in this release have been uploaded with provenance metadata.
Attestation for libigl-2.6.4.dev3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA 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.
