18.0k GitHub stars and counting — pybind/pybind11 is a C++ project TopGit is tracking across repositories on the platform. Seamless operability between C++11 and Python
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Setuptools example <https://github.com/pybind/python_example>_
• Scikit-build example <https://github.com/pybind/scikit_build_example>_
• CMake example <https://github.com/pybind/cmake_example>_
.. start
pybind11 is a lightweight header-only library that exposes C++ types
in Python and vice versa, mainly to create Python bindings of existing
C++ code. Its goals and syntax are similar to the excellent
Boost.Python <http://www.boost.org/doc/libs/1_58_0/libs/python/doc/>_
library by David Abrahams: to minimize boilerplate code in traditional
extension modules by inferring type information using compile-time
introspection.
The main issue with Boost.Python—and the reason for creating such a
similar project—is Boost. Boost is an enormously large and complex suite
of utility libraries that works with almost every C++ compiler in
existence. This compatibility has its cost: arcane template tricks and
workarounds are necessary to support the oldest and buggiest of compiler
specimens. Now that C++11-compatible compilers are widely available,
this heavy machinery has become an excessively large and unnecessary
dependency.
Think of this library as a tiny self-contained version of Boost.Python
with everything stripped away that isn't relevant for binding
generation. Without comments, the core header files only require ~4K
lines of code and depend on Python (CPython 3.9+, PyPy, or GraalPy) and the C++
standard library. This compact implementation was possible thanks to some C++11
language features (specifically: tuples, lambda functions and variadic
templates). Since its creation, this library has grown beyond Boost.Python in
many ways, leading to dramatically simpler binding code in many common
situations.
Tutorial and reference documentation is provided at
pybind11.readthedocs.io <https://pybind11.readthedocs.io/en/latest>.
A PDF version of the manual is available
here <https://pybind11.readthedocs.io/_/downloads/en/latest/pdf/>.
And the source code is always available at
github.com/pybind/pybind11 <https://github.com/pybind/pybind11>_.
Core features
pybind11 can map the following core C++ features to Python:
Functions accepting and returning custom data structures per value,
reference, or pointer
Instance methods and static methods
Overloaded functions
Instance attributes and static attributes
Arbitrary exception types
Enumerations
Callbacks
Iterators and ranges
Custom operators
Single and multiple inheritance
STL data structures
Smart pointers with reference counting like std::shared_ptr
Internal references with correct reference counting
C++ classes with virtual (and pure virtual) methods can be extended
in Python
Integrated NumPy support (NumPy 2 requires pybind11 2.12+)
Goodies
In addition to the core functionality, pybind11 provides some extra
goodies:
CPython 3.9+, PyPy3 7.3.17+, and GraalPy 24.1+ are supported with an
implementation-agnostic interface (see older versions for older CPython
and PyPy versions).
It is possible to bind C++11 lambda functions with captured
variables. The lambda capture data is stored inside the resulting
Python function object.
pybind11 uses C++11 move constructors and move assignment operators
whenever possible to efficiently transfer custom data types.
It's easy to expose the internal storage of custom data types through
Pythons' buffer protocols. This is handy e.g. for fast conversion
between C++ matrix classes like Eigen and NumPy without expensive
copy operations.
pybind11 can automatically vectorize functions so that they are
transparently applied to all entries of one or more NumPy array
arguments.
Python's slice-based access and assignment operations can be
supported with just a few lines of code.
Everything is contained in just a few header files; there is no need
to link against any additional libraries.
Binaries are generally smaller by a factor of at least 2 compared to
equivalent bindings generated by Boost.Python. A recent pybind11
conversion of PyRosetta, an enormous Boost.Python binding project,
reported <https://graylab.jhu.edu/Sergey/2016.RosettaCon/PyRosetta-4.pdf>_
a binary size reduction of 5.4x and compile time reduction by
5.8x.
Function signatures are precomputed at compile time (using
constexpr), leading to smaller binaries.
With little extra effort, C++ types can be pickled and unpickled
similar to regular Python objects.
Supported platforms & compilers
pybind11 is exercised in continuous integration across a range of operating
systems, Python versions, C++ standards, and toolchains. For an up-to-date
view of the combinations we currently test, please see the
pybind11 GitHub Actions <https://github.com/pybind/pybind11/actions?query=branch%3Amaster>_
and AppVeyor <https://ci.appveyor.com/project/wjakob/pybind11>_ logs.
The test matrix naturally evolves over time as older platforms and compilers
fall out of use and new ones are added by the community. Closely related
versions of a tested compiler or platform will often work as well in practice,
but we cannot promise to validate every possible combination. If a
configuration you rely on is missing from the matrix or regresses, issues and
pull requests to extend coverage are very welcome. At the same time, we need
to balance the size of the test matrix with the available CI resources,
such as GitHub's limits on concurrent jobs under the free tier.
About
This project was created by Wenzel Jakob <http://rgl.epfl.ch/people/wjakob>_. Significant features and/or
improvements to the code were contributed by
Jonas Adler,
Lori A. Burns,
Sylvain Corlay,
Eric Cousineau,
Aaron Gokaslan,
Ralf Grosse-Kunstleve,
Trent Houliston,
Axel Huebl,
@hulucc,
Yannick Jadoul,
Sergey Lyskov,
Johan Mabille,
Tomasz Miąsko,
Dean Moldovan,
Ben Pritchard,
Jason Rhinelander,
Boris Schäling,
Pim Schellart,
Henry Schreiner,
Ivan Smirnov,
Dustin Spicuzza,
Boris Staletic,
Ethan Steinberg,
Patrick Stewart,
Ivor Wanders,
and
Xiaofei Wang.
We thank Google for a generous financial contribution to the continuous
integration infrastructure used by this project.
Contributing
See the `contributing
guide <https://github.com/pybind/pybind11/blob/master/.github/CONTRIBUTING.md>`_
for information on building and contributing to pybind11.
License
~~~~~~~
pybind11 is provided under a BSD-style license that can be found in the
`LICENSE <https://github.com/pybind/pybind11/blob/master/LICENSE>`_
file. By using, distributing, or contributing to this project, you agree
to the terms and conditions of this license.
.. |Latest Documentation Status| image:: https://readthedocs.org/projects/pybind11/badge?version=latest
:target: http://pybind11.readthedocs.org/en/latest
.. |Stable Documentation Status| image:: https://img.shields.io/badge/docs-stable-blue.svg
:target: http://pybind11.readthedocs.org/en/stable
.. |Gitter chat| image:: https://img.shields.io/gitter/room/gitterHQ/gitter.svg
:target: https://gitter.im/pybind/Lobby
.. |CI| image:: https://github.com/pybind/pybind11/workflows/CI/badge.svg
:target: https://github.com/pybind/pybind11/actions
.. |Build status| image:: https://ci.appveyor.com/api/projects/status/riaj54pn4h08xy40?svg=true
:target: https://ci.appveyor.com/project/wjakob/pybind11
.. |PyPI package| image:: https://img.shields.io/pypi/v/pybind11.svg
:target: https://pypi.org/project/pybind11/
.. |Conda-forge| image:: https://img.shields.io/conda/vn/conda-forge/pybind11.svg
:target: https://github.com/conda-forge/pybind11-feedstock
.. |Repology| image:: https://repology.org/badge/latest-versions/python:pybind11.svg
:target: https://repology.org/project/python:pybind11/versions
.. |Python Versions| image:: https://img.shields.io/pypi/pyversions/pybind11.svg
:target: https://pypi.org/project/pybind11/
.. |GitHub Discussions| image:: https://img.shields.io/static/v1?label=Discussions&message=Ask&color=blue&logo=github
:target: https://github.com/pybind/pybind11/discussions
.. |SPEC 4 — Using and Creating Nightly Wheels| image:: https://img.shields.io/badge/SPEC-4-green?labelColor=%23004811&color=%235CA038
:target: https://scientific-python.org/specs/spec-0004/
The most recent commit recorded on pybind/pybind11 was 12 days ago, based on the GitHub push timestamp. The repository has 2.3k forks — one of the better signals of community interest.
How many stars does pybind/pybind11 have?
pybind/pybind11 has 18.0k GitHub stars — refresh the page for the live number, or check github.com/pybind/pybind11. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the Backend space?
pybind/pybind11 is tracked by TopGit under the Backend category, alongside 2 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is pybind/pybind11 written in?
pybind/pybind11 is written primarily in C++. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is pybind/pybind11 associated with?
GitHub's repository topics for pybind/pybind11: "bindings", "python". TopGit's editorial category is Backend.
Where do I read more about pybind/pybind11?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/pybind/pybind11 is the definitive source.
Why is pybind/pybind11 categorized under Backend?
TopGit places pybind/pybind11 in the Backend category based on its GitHub topics and description (tagged: "bindings", "python"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Want a second opinion on pybind11?
Ask an AI that can read this page — one click and you get its take on pybind11.
/pybind11