| commit | 3f589379ec04c2c2a677ffc060418db151c61cd0 | [log] [tgz] |
|---|---|---|
| author | Jason Rhinelander <jason@imaginary.ca> | Sun Aug 07 13:05:26 2016 -0400 |
| committer | Jason Rhinelander <jason@imaginary.ca> | Thu Aug 11 18:16:04 2016 -0400 |
| tree | 0b3802ab53104392fd108297792a42427c2a722e | |
| parent | 85557b1dec178665a05af4002507af0570a3038d [diff] |
Improve constructor/destructor tracking This commit rewrites the examples that look for constructor/destructor calls to do so via static variable tracking rather than output parsing. The added ConstructorStats class provides methods to keep track of constructors and destructors, number of default/copy/move constructors, and number of copy/move assignments. It also provides a mechanism for storing values (e.g. for value construction), and then allows all of this to be checked at the end of a test by getting the statistics for a C++ (or python mapping) class. By not relying on the precise pattern of constructions/destructions, but rather simply ensuring that every construction is matched with a destruction on the same object, we ensure that everything that gets created also gets destroyed as expected. This replaces all of the various "std::cout << whatever" code in constructors/destructors with `print_created(this)`/`print_destroyed(this)`/etc. functions which provide similar output, but now has a unified format across the different examples, including a new ### prefix that makes mixed example output and lifecycle events easier to distinguish. With this change, relaxed mode is no longer needed, which enables testing for proper destruction under MSVC, and under any other compiler that generates code calling extra constructors, or optimizes away any constructors. GCC/clang are used as the baseline for move constructors; the tests are adapted to allow more move constructors to be evoked (but other types are constructors much have matching counts). This commit also disables output buffering of tests, as the buffering sometimes results in C++ output ending up in the middle of python output (or vice versa), depending on the OS/python version.
- example/CMakeLists.txt[diff]
- example/constructor-stats.h[Added - diff]
- example/example-buffers.cpp[diff]
- example/example-buffers.py[diff]
- example/example-buffers.ref[diff]
- example/example-callbacks.cpp[diff]
- example/example-callbacks.py[diff]
- example/example-callbacks.ref[diff]
- example/example-methods-and-attributes.cpp[diff]
- example/example-methods-and-attributes.py[diff]
- example/example-methods-and-attributes.ref[diff]
- example/example-modules.cpp[diff]
- example/example-modules.py[diff]
- example/example-modules.ref[diff]
- example/example-opaque-types.py[diff]
- example/example-opaque-types.ref[diff]
- example/example-operator-overloading.cpp[diff]
- example/example-operator-overloading.py[diff]
- example/example-operator-overloading.ref[diff]
- example/example-python-types.cpp[diff]
- example/example-python-types.py[diff]
- example/example-python-types.ref[diff]
- example/example-sequences-and-iterators.cpp[diff]
- example/example-sequences-and-iterators.py[diff]
- example/example-sequences-and-iterators.ref[diff]
- example/example-smart-ptr.cpp[diff]
- example/example-smart-ptr.py[diff]
- example/example-smart-ptr.ref[diff]
- example/example-virtual-functions.cpp[diff]
- example/example-virtual-functions.py[diff]
- example/example-virtual-functions.ref[diff]
- example/example.cpp[diff]
- example/issues.cpp[diff]
- example/issues.ref[diff]
- example/object.h[diff]
- example/run_test.py[diff]
- docs/
- example/
- include/
- pybind11/
- tools/
- .appveyor.yml
- .gitignore
- .gitmodules
- .travis.yml
- CMakeLists.txt
- CONTRIBUTING.md
- LICENSE
- MANIFEST.in
- README.md
- setup.cfg
- setup.py
pybind11 — Seamless operability between C++11 and Python
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 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 ~2.5K lines of code and depend on Python (2.7 or 3.x) and the C++ standard library. This compact implementation was possible thanks to some of the new 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 http://pybind11.readthedocs.org/en/latest. A PDF version of the manual is available here.
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
- Custom operators
- STL data structures
- Iterators and ranges
- 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
Goodies
In addition to the core functionality, pybind11 provides some extra goodies:
pybind11 uses C++11 move constructors and move assignment operators whenever possible to efficiently transfer custom data types.
It is possible to bind C++11 lambda functions with captured variables. The lambda capture data is stored inside the resulting Python function object.
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 2 or more compared to equivalent bindings generated by Boost.Python.
When supported by the compiler, two new C++14 features (relaxed constexpr and return value deduction) are used to precompute function signatures at compile time, leading to smaller binaries.
With little extra effort, C++ types can be pickled and unpickled similar to regular Python objects.
Supported compilers
- Clang/LLVM (any non-ancient version with C++11 support)
- GCC (any non-ancient version with C++11 support)
- Microsoft Visual Studio 2015 or newer
- Intel C++ compiler 16 or newer (15 with a workaround)
- Cygwin/GCC (tested on 2.5.1)
About
This project was created by Wenzel Jakob. Significant features and/or improvements to the code were contributed by Jonas Adler, Sylvain Corlay, Axel Huebl, @hulucc, Sergey Lyskov Johan Mabille, Tomasz Miąsko, Dean Moldovan, Ben Pritchard, Boris Schäling, and Pim Schellart.
License
pybind11 is provided under a BSD-style license that can be found in the LICENSE file. By using, distributing, or contributing to this project, you agree to the terms and conditions of this license.