commit	b3f3d79f4c5ea6217f9028d2971b6538dd010ac6	[log] [tgz]
author	Jason Rhinelander <jason@imaginary.ca>	Mon Jul 18 16:43:18 2016 -0400
committer	Jason Rhinelander <jason@imaginary.ca>	Mon Jul 18 16:43:18 2016 -0400
tree	33200b9b348f387f87064416b384c31ae3dc35a4
parent	fb6aed21576f1de5e6b54f4a8279a7f64a717b30 [diff]

Rename examples files, as per #288

This renames example files from `exampleN` to `example-description`.

Specifically, the following renaming is applied:

example1 -> example-methods-and-attributes
example2 -> example-python-types
example3 -> example-operator-overloading
example4 -> example-constants-and-functions
example5 -> example-callbacks (*)
example6 -> example-sequence-and-iterators
example7 -> example-buffers
example8 -> example-custom-ref-counting
example9 -> example-modules
example10 -> example-numpy-vectorize
example11 -> example-arg-keywords-and-defaults
example12 -> example-virtual-functions
example13 -> example-keep-alive
example14 -> example-opaque-types
example15 -> example-pickling
example16 -> example-inheritance
example17 -> example-stl-binders
example18 -> example-eval
example19 -> example-custom-exceptions

* the inheritance parts of example5 are moved into example-inheritance
(previously example16), and the remainder is left as example-callbacks.

This commit also renames the internal variables ("Example1",
"Example2", "Example4", etc.) into non-numeric names ("ExampleMandA",
"ExamplePythonTypes", "ExampleWithEnum", etc.) to correspond to the
file renaming.

The order of tests is preserved, but this can easily be changed if
there is some more natural ordering by updating the list in
examples/CMakeLists.txt.

example/CMakeLists.txt[diff]
example/example-arg-keywords-and-defaults.cpp[Renamed from example/example11.cpp - diff]
example/example-arg-keywords-and-defaults.py[Renamed from example/example11.py - diff]
example/example-arg-keywords-and-defaults.ref[Renamed from example/example11.ref - diff]
example/example-buffers.cpp[Renamed from example/example7.cpp - diff]
example/example-buffers.py[Renamed from example/example7.py - diff]
example/example-buffers.ref[Renamed from example/example7.ref - diff]
example/example-callbacks.cpp[Renamed from example/example5.cpp - diff]
example/example-callbacks.py[Renamed from example/example5.py - diff]
example/example-callbacks.ref[Renamed from example/example5.ref - diff]
example/example-constants-and-functions.cpp[Renamed from example/example4.cpp - diff]
example/example-constants-and-functions.py[Added - diff]
example/example-constants-and-functions.ref[Added - diff]
example/example-custom-exceptions.cpp[Renamed from example/example19.cpp - diff]
example/example-custom-exceptions.py[Renamed from example/example19.py - diff]
example/example-custom-exceptions.ref[Renamed from example/example19.ref - diff]
example/example-eval.cpp[Renamed from example/example18.cpp - diff]
example/example-eval.py[Added - diff]
example/example-eval.ref[Renamed from example/example18.ref - diff]
example/example-eval_call.py[Renamed from example/example18_call.py - diff]
example/example-inheritance.cpp[Added - diff]
example/example-inheritance.py[Renamed from example/example16.py - diff]
example/example-inheritance.ref[Renamed from example/example16.ref - diff]
example/example-keep-alive.cpp[Renamed from example/example13.cpp - diff]
example/example-keep-alive.py[Renamed from example/example13.py - diff]
example/example-keep-alive.ref[Renamed from example/example13.ref - diff]
example/example-methods-and-attributes.cpp[Added - diff]
example/example-methods-and-attributes.py[Renamed from example/example1.py - diff]
example/example-methods-and-attributes.ref[Added - diff]
example/example-modules.cpp[Renamed from example/example9.cpp - diff]
example/example-modules.py[Renamed from example/example9.py - diff]
example/example-modules.ref[Renamed from example/example9.ref - diff]
example/example-numpy-vectorize.cpp[Renamed from example/example10.cpp - diff]
example/example-numpy-vectorize.py[Renamed from example/example10.py - diff]
example/example-numpy-vectorize.ref[Renamed from example/example10.ref - diff]
example/example-opaque-types.cpp[Renamed from example/example14.cpp - diff]
example/example-opaque-types.py[Renamed from example/example14.py - diff]
example/example-opaque-types.ref[Renamed from example/example14.ref - diff]
example/example-operator-overloading.cpp[Renamed from example/example3.cpp - diff]
example/example-operator-overloading.py[Renamed from example/example3.py - diff]
example/example-operator-overloading.ref[Renamed from example/example3.ref - diff]
example/example-pickling.cpp[Renamed from example/example15.cpp - diff]
example/example-pickling.py[Renamed from example/example15.py - diff]
example/example-pickling.ref[Renamed from example/example15.ref - diff]
example/example-python-types.cpp[Renamed from example/example2.cpp - diff]
example/example-python-types.py[Renamed from example/example2.py - diff]
example/example-python-types.ref[Renamed from example/example2.ref - diff]
example/example-sequences-and-iterators.cpp[Renamed from example/example6.cpp - diff]
example/example-sequences-and-iterators.py[Renamed from example/example6.py - diff]
example/example-sequences-and-iterators.ref[Renamed from example/example6.ref - diff]
example/example-smart-ptr.cpp[Renamed from example/example8.cpp - diff]
example/example-smart-ptr.py[Renamed from example/example8.py - diff]
example/example-smart-ptr.ref[Renamed from example/example8.ref - diff]
example/example-stl-binder-vector.cpp[Renamed from example/example17.cpp - diff]
example/example-stl-binder-vector.py[Renamed from example/example17.py - diff]
example/example-stl-binder-vector.ref[Renamed from example/example17.ref - diff]
example/example-virtual-functions.cpp[Added - diff]
example/example-virtual-functions.py[Added - diff]
example/example-virtual-functions.ref[Added - diff]
example/example.cpp[diff]
example/example1.cpp[Deleted - diff]
example/example1.ref[Deleted - diff]
example/example12.cpp[Deleted - diff]
example/example12.py[Deleted - diff]
example/example12.ref[Deleted - diff]
example/example16.cpp[Deleted - diff]
example/example18.py[Deleted - diff]
example/example4.py[Deleted - diff]
example/example4.ref[Deleted - diff]
example/run_test.py[diff]

70 files changed

tree: 33200b9b348f387f87064416b384c31ae3dc35a4

README.md

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.