epython
nanobind
| epython | nanobind | |
|---|---|---|
| 1 | 11 | |
| 40 | 2,071 | |
| - | - | |
| 0.0 | 9.6 | |
| about 2 years ago | 6 days ago | |
| Python | C++ | |
| BSD 3-clause "New" or "Revised" License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
epython
-
Cython Is 20
This is related to the idea of EPython that we are working on (as we have funding): https://github.com/epython-dev/epython
It currently emits Cython for the C-backend (and PyIodide). It is very alpha currently, but if people are interested in helping, get in touch.
nanobind
-
Progress on No-GIL CPython
Take a look at https://github.com/wjakob/nanobind
> More concretely, benchmarks show up to ~4× faster compile time, ~5× smaller binaries, and ~10× lower runtime overheads compared to pybind11.
-
Advanced Python Mastery – A Course by David Beazley
People should not take that an endorsement of Swig.
Please use ctypes, cffi or https://github.com/wjakob/nanobind
Beazley himself is amazed that it (Swig) is still in use.
- Swig – Connect C/C++ programs with high-level programming languages
- Nanobind: Tiny and efficient C++/Python bindings
-
Create Python bindings for my C++ code with PyBind11
Nanobind made by the creator of PyBind11, it has a similar interface, but it takes leverage of C++17 and it aims to have more efficient bindings in space and speed.
- Nanobind – Seamless operability between C++17 and Python
-
Cython Is 20
I would recommend using NanoBind, the follow up of PyBind11 by the same author (Wensel Jakob), and move as much performance critical code to C or C++. https://github.com/wjakob/nanobind
If you really care about performance called from Python, consider something like NVIDIA Warp (Preview). Warp jits and runs your code on CUDA or CPU. Although Warp targets physics simulation, geometry processing, and procedural animation, it can be used for other tasks as well. https://github.com/NVIDIA/warp
Jax is another option, by Google, jitting and vectorizing code for TPU, GPU or CPU. https://github.com/google/jax
- GitHub - wjakob/nanobind: nanobind — Seamless operability between C++17 and Python
What are some alternatives?
Nuitka - Nuitka is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11. You feed it your Python app, it does a lot of clever things, and spits out an executable or extension module.
pybind11 - Seamless operability between C++11 and Python