2015-10-15 16:24:12 +00:00
|
|
|
#!/usr/bin/env python
|
|
|
|
|
|
2016-08-12 11:50:00 +00:00
|
|
|
# Setup script for PyPI; use CMakeFile.txt to build extension modules
|
2015-10-15 16:24:12 +00:00
|
|
|
|
|
|
|
|
from setuptools import setup
|
2017-08-23 12:20:53 +00:00
|
|
|
from distutils.command.install_headers import install_headers
|
2016-03-01 09:36:10 +00:00
|
|
|
from pybind11 import __version__
|
2017-02-14 12:16:14 +00:00
|
|
|
import os
|
2015-10-15 16:24:12 +00:00
|
|
|
|
2017-02-14 12:16:14 +00:00
|
|
|
# Prevent installation of pybind11 headers by setting
|
|
|
|
|
# PYBIND11_USE_CMAKE.
|
|
|
|
|
if os.environ.get('PYBIND11_USE_CMAKE'):
|
|
|
|
|
headers = []
|
|
|
|
|
else:
|
|
|
|
|
headers = [
|
2017-08-13 22:35:53 +00:00
|
|
|
'include/pybind11/detail/class.h',
|
|
|
|
|
'include/pybind11/detail/common.h',
|
|
|
|
|
'include/pybind11/detail/descr.h',
|
Allow binding factory functions as constructors
This allows you to use:
cls.def(py::init(&factory_function));
where `factory_function` returns a pointer, holder, or value of the
class type (or a derived type). Various compile-time checks
(static_asserts) are performed to ensure the function is valid, and
various run-time type checks where necessary.
Some other details of this feature:
- The `py::init` name doesn't conflict with the templated no-argument
`py::init<...>()`, but keeps the naming consistent: the existing
templated, no-argument one wraps constructors, the no-template,
function-argument one wraps factory functions.
- If returning a CppClass (whether by value or pointer) when an CppAlias
is required (i.e. python-side inheritance and a declared alias), a
dynamic_cast to the alias is attempted (for the pointer version); if
it fails, or if returned by value, an Alias(Class &&) constructor
is invoked. If this constructor doesn't exist, a runtime error occurs.
- for holder returns when an alias is required, we try a dynamic_cast of
the wrapped pointer to the alias to see if it is already an alias
instance; if it isn't, we raise an error.
- `py::init(class_factory, alias_factory)` is also available that takes
two factories: the first is called when an alias is not needed, the
second when it is.
- Reimplement factory instance clearing. The previous implementation
failed under python-side multiple inheritance: *each* inherited
type's factory init would clear the instance instead of only setting
its own type value. The new implementation here clears just the
relevant value pointer.
- dealloc is updated to explicitly set the leftover value pointer to
nullptr and the `holder_constructed` flag to false so that it can be
used to clear preallocated value without needing to rebuild the
instance internals data.
- Added various tests to test out new allocation/deallocation code.
- With preallocation now done lazily, init factory holders can
completely avoid the extra overhead of needing an extra
allocation/deallocation.
- Updated documentation to make factory constructors the default
advanced constructor style.
- If an `__init__` is called a second time, we have two choices: we can
throw away the first instance, replacing it with the second; or we can
ignore the second call. The latter is slightly easier, so do that.
2017-06-13 01:52:48 +00:00
|
|
|
'include/pybind11/detail/init.h',
|
2017-08-20 14:15:33 +00:00
|
|
|
'include/pybind11/detail/internals.h',
|
2017-08-23 12:20:53 +00:00
|
|
|
'include/pybind11/detail/typeid.h',
|
2016-01-17 21:36:44 +00:00
|
|
|
'include/pybind11/attr.h',
|
2017-05-07 16:19:19 +00:00
|
|
|
'include/pybind11/buffer_info.h',
|
2015-10-15 16:24:12 +00:00
|
|
|
'include/pybind11/cast.h',
|
2016-12-01 14:22:17 +00:00
|
|
|
'include/pybind11/chrono.h',
|
2017-09-04 21:22:22 +00:00
|
|
|
'include/pybind11/common.h',
|
2015-10-15 16:24:12 +00:00
|
|
|
'include/pybind11/complex.h',
|
2016-05-05 18:33:54 +00:00
|
|
|
'include/pybind11/eigen.h',
|
2017-03-29 22:20:42 +00:00
|
|
|
'include/pybind11/embed.h',
|
2016-12-01 14:22:17 +00:00
|
|
|
'include/pybind11/eval.h',
|
|
|
|
|
'include/pybind11/functional.h',
|
2017-08-25 00:12:43 +00:00
|
|
|
'include/pybind11/iostream.h',
|
2015-10-15 16:24:12 +00:00
|
|
|
'include/pybind11/numpy.h',
|
2016-12-01 14:22:17 +00:00
|
|
|
'include/pybind11/operators.h',
|
|
|
|
|
'include/pybind11/options.h',
|
2015-10-15 16:24:12 +00:00
|
|
|
'include/pybind11/pybind11.h',
|
2016-12-01 14:22:17 +00:00
|
|
|
'include/pybind11/pytypes.h',
|
2015-10-15 16:24:12 +00:00
|
|
|
'include/pybind11/stl.h',
|
2016-05-15 18:50:38 +00:00
|
|
|
'include/pybind11/stl_bind.h',
|
2017-02-14 12:16:14 +00:00
|
|
|
]
|
|
|
|
|
|
2017-08-23 12:20:53 +00:00
|
|
|
|
|
|
|
|
class InstallHeaders(install_headers):
|
|
|
|
|
"""Use custom header installer because the default one flattens subdirectories"""
|
|
|
|
|
def run(self):
|
|
|
|
|
if not self.distribution.headers:
|
|
|
|
|
return
|
|
|
|
|
|
|
|
|
|
for header in self.distribution.headers:
|
|
|
|
|
subdir = os.path.dirname(os.path.relpath(header, 'include/pybind11'))
|
|
|
|
|
install_dir = os.path.join(self.install_dir, subdir)
|
|
|
|
|
self.mkpath(install_dir)
|
|
|
|
|
|
|
|
|
|
(out, _) = self.copy_file(header, install_dir)
|
|
|
|
|
self.outfiles.append(out)
|
|
|
|
|
|
|
|
|
|
|
2017-02-14 12:16:14 +00:00
|
|
|
setup(
|
|
|
|
|
name='pybind11',
|
|
|
|
|
version=__version__,
|
|
|
|
|
description='Seamless operability between C++11 and Python',
|
|
|
|
|
author='Wenzel Jakob',
|
|
|
|
|
author_email='wenzel.jakob@epfl.ch',
|
|
|
|
|
url='https://github.com/wjakob/pybind11',
|
|
|
|
|
download_url='https://github.com/wjakob/pybind11/tarball/v' + __version__,
|
|
|
|
|
packages=['pybind11'],
|
|
|
|
|
license='BSD',
|
|
|
|
|
headers=headers,
|
2017-08-23 12:20:53 +00:00
|
|
|
cmdclass=dict(install_headers=InstallHeaders),
|
2015-10-15 16:24:12 +00:00
|
|
|
classifiers=[
|
|
|
|
|
'Development Status :: 5 - Production/Stable',
|
|
|
|
|
'Intended Audience :: Developers',
|
|
|
|
|
'Topic :: Software Development :: Libraries :: Python Modules',
|
|
|
|
|
'Topic :: Utilities',
|
|
|
|
|
'Programming Language :: C++',
|
|
|
|
|
'Programming Language :: Python :: 2.7',
|
|
|
|
|
'Programming Language :: Python :: 3',
|
|
|
|
|
'Programming Language :: Python :: 3.2',
|
|
|
|
|
'Programming Language :: Python :: 3.3',
|
|
|
|
|
'Programming Language :: Python :: 3.4',
|
2015-10-15 20:43:55 +00:00
|
|
|
'Programming Language :: Python :: 3.5',
|
2017-01-01 16:14:27 +00:00
|
|
|
'Programming Language :: Python :: 3.6',
|
|
|
|
|
'License :: OSI Approved :: BSD License'
|
2015-10-15 16:24:12 +00:00
|
|
|
],
|
|
|
|
|
keywords='C++11, Python bindings',
|
2017-01-01 16:14:27 +00:00
|
|
|
long_description="""pybind11 is a lightweight header-only library that
|
|
|
|
|
exposes C++ types in Python and vice versa, mainly to create Python bindings of
|
2015-10-15 16:24:12 +00:00
|
|
|
existing C++ code. Its goals and syntax are similar to the excellent
|
2017-01-01 16:14:27 +00:00
|
|
|
Boost.Python by David Abrahams: to minimize boilerplate code in traditional
|
|
|
|
|
extension modules by inferring type information using compile-time
|
2015-10-15 16:24:12 +00:00
|
|
|
introspection.
|
|
|
|
|
|
2017-01-04 14:17:18 +00:00
|
|
|
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
|
2015-10-15 16:24:12 +00:00
|
|
|
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
|
2016-01-17 21:36:44 +00:00
|
|
|
everything stripped away that isn't relevant for binding generation. Without
|
2017-01-01 16:14:27 +00:00
|
|
|
comments, the core header files only require ~4K lines of code and depend on
|
|
|
|
|
Python (2.7 or 3.x, or PyPy2.7 >= 5.7) 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.""")
|
