pybind11/tests/pybind11_tests.h

#pragma once
#include <pybind11/pybind11.h>
#include <functional>
#include <list>

namespace py = pybind11;
using namespace pybind11::literals;

class test_initializer {
public:
    test_initializer(std::function<void(py::module &)> initializer);
};
Make test initialization self-registering Adding or removing tests is a little bit cumbersome currently: the test needs to be added to CMakeLists.txt, the init function needs to be predeclared in pybind11_tests.cpp, then called in the plugin initialization. While this isn't a big deal for tests that are being committed, it's more of a hassle when working on some new feature or test code for which I temporarily only care about building and linking the test being worked on rather than the entire test suite. This commit changes tests to self-register their initialization by having each test initialize a local object (which stores the initialization function in a static variable). This makes changing the set of tests being build easy: one only needs to add or comment out test names in tests/CMakeLists.txt. A couple other minor changes that go along with this: - test_eigen.cpp is now included in the test list, then removed if eigen isn't available. This lets you disable the eigen tests by commenting it out, just like all the other tests, but keeps the build working without eigen eigen isn't available. (Also, if it's commented out, we don't even bother looking for and reporting the building with/without eigen status message). - pytest is now invoked with all the built test names (with .cpp changed to .py) so that it doesn't try to run tests that weren't built. 2016-09-03 18:54:22 +00:00			`#pragma once`
last breaking change: be consistent about the project name 2015-10-15 16:13:33 +00:00			`#include <pybind11/pybind11.h>`
Make test initialization self-registering Adding or removing tests is a little bit cumbersome currently: the test needs to be added to CMakeLists.txt, the init function needs to be predeclared in pybind11_tests.cpp, then called in the plugin initialization. While this isn't a big deal for tests that are being committed, it's more of a hassle when working on some new feature or test code for which I temporarily only care about building and linking the test being worked on rather than the entire test suite. This commit changes tests to self-register their initialization by having each test initialize a local object (which stores the initialization function in a static variable). This makes changing the set of tests being build easy: one only needs to add or comment out test names in tests/CMakeLists.txt. A couple other minor changes that go along with this: - test_eigen.cpp is now included in the test list, then removed if eigen isn't available. This lets you disable the eigen tests by commenting it out, just like all the other tests, but keeps the build working without eigen eigen isn't available. (Also, if it's commented out, we don't even bother looking for and reporting the building with/without eigen status message). - pytest is now invoked with all the built test names (with .cpp changed to .py) so that it doesn't try to run tests that weren't built. 2016-09-03 18:54:22 +00:00			`#include <functional>`
			`#include <list>`
Initial commit 2015-07-05 18:05:44 +00:00
last breaking change: be consistent about the project name 2015-10-15 16:13:33 +00:00			`namespace py = pybind11;`
Support keyword arguments and generalized unpacking in C++ A Python function can be called with the syntax: ```python foo(a1, a2, args, ka=1, kb=2, kwargs) ``` This commit adds support for the equivalent syntax in C++: ```c++ foo(a1, a2, args, "ka"_a=1, "kb"_a=2, *kwargs) ``` In addition, generalized unpacking is implemented, as per PEP 448, which allows calls with multiple and ** unpacking: ```python bar(args1, 99, args2, 101, kwargs1, kz=200, kwargs2) ``` and ```c++ bar(args1, 99, args2, 101, kwargs1, "kz"_a=200, kwargs2) ``` 2016-08-29 01:05:42 +00:00			`using namespace pybind11::literals;`
Make test initialization self-registering Adding or removing tests is a little bit cumbersome currently: the test needs to be added to CMakeLists.txt, the init function needs to be predeclared in pybind11_tests.cpp, then called in the plugin initialization. While this isn't a big deal for tests that are being committed, it's more of a hassle when working on some new feature or test code for which I temporarily only care about building and linking the test being worked on rather than the entire test suite. This commit changes tests to self-register their initialization by having each test initialize a local object (which stores the initialization function in a static variable). This makes changing the set of tests being build easy: one only needs to add or comment out test names in tests/CMakeLists.txt. A couple other minor changes that go along with this: - test_eigen.cpp is now included in the test list, then removed if eigen isn't available. This lets you disable the eigen tests by commenting it out, just like all the other tests, but keeps the build working without eigen eigen isn't available. (Also, if it's commented out, we don't even bother looking for and reporting the building with/without eigen status message). - pytest is now invoked with all the built test names (with .cpp changed to .py) so that it doesn't try to run tests that weren't built. 2016-09-03 18:54:22 +00:00
			`class test_initializer {`
			`public:`
			`test_initializer(std::function<void(py::module &)> initializer);`
			`};`