2015-07-05 18:05:44 +00:00
|
|
|
/*
|
2016-08-12 11:50:00 +00:00
|
|
|
tests/pybind11_tests.cpp -- pybind example plugin
|
2015-07-05 18:05:44 +00:00
|
|
|
|
2016-04-17 18:21:41 +00:00
|
|
|
Copyright (c) 2016 Wenzel Jakob <wenzel.jakob@epfl.ch>
|
2015-07-05 18:05:44 +00:00
|
|
|
|
|
|
|
All rights reserved. Use of this source code is governed by a
|
|
|
|
BSD-style license that can be found in the LICENSE file.
|
|
|
|
*/
|
|
|
|
|
2016-08-12 11:50:00 +00:00
|
|
|
#include "pybind11_tests.h"
|
2022-02-10 20:17:07 +00:00
|
|
|
|
2016-08-12 11:50:00 +00:00
|
|
|
#include "constructor_stats.h"
|
2015-07-05 18:05:44 +00:00
|
|
|
|
2017-06-08 22:44:49 +00:00
|
|
|
#include <functional>
|
|
|
|
#include <list>
|
|
|
|
|
2017-02-01 09:36:29 +00:00
|
|
|
/*
|
|
|
|
For testing purposes, we define a static global variable here in a function that each individual
|
|
|
|
test .cpp calls with its initialization lambda. It's convenient here because we can just not
|
|
|
|
compile some test files to disable/ignore some of the test code.
|
|
|
|
|
|
|
|
It is NOT recommended as a way to use pybind11 in practice, however: the initialization order will
|
|
|
|
be essentially random, which is okay for our test scripts (there are no dependencies between the
|
|
|
|
individual pybind11 test .cpp files), but most likely not what you want when using pybind11
|
|
|
|
productively.
|
|
|
|
|
|
|
|
Instead, see the "How can I reduce the build time?" question in the "Frequently asked questions"
|
|
|
|
section of the documentation for good practice on splitting binding code over multiple files.
|
|
|
|
*/
|
2020-10-03 17:38:03 +00:00
|
|
|
std::list<std::function<void(py::module_ &)>> &initializers() {
|
|
|
|
static std::list<std::function<void(py::module_ &)>> inits;
|
2016-09-03 18:54:22 +00:00
|
|
|
return inits;
|
|
|
|
}
|
2015-07-05 18:05:44 +00:00
|
|
|
|
2022-02-10 20:17:07 +00:00
|
|
|
test_initializer::test_initializer(Initializer init) { initializers().emplace_back(init); }
|
2017-06-08 22:44:49 +00:00
|
|
|
|
|
|
|
test_initializer::test_initializer(const char *submodule_name, Initializer init) {
|
2020-10-03 17:38:03 +00:00
|
|
|
initializers().emplace_back([=](py::module_ &parent) {
|
2017-06-08 22:44:49 +00:00
|
|
|
auto m = parent.def_submodule(submodule_name);
|
|
|
|
init(m);
|
|
|
|
});
|
2016-09-03 18:54:22 +00:00
|
|
|
}
|
2016-05-05 18:33:54 +00:00
|
|
|
|
2020-10-03 17:38:03 +00:00
|
|
|
void bind_ConstructorStats(py::module_ &m) {
|
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.
2016-08-07 17:05:26 +00:00
|
|
|
py::class_<ConstructorStats>(m, "ConstructorStats")
|
|
|
|
.def("alive", &ConstructorStats::alive)
|
|
|
|
.def("values", &ConstructorStats::values)
|
|
|
|
.def_readwrite("default_constructions", &ConstructorStats::default_constructions)
|
|
|
|
.def_readwrite("copy_assignments", &ConstructorStats::copy_assignments)
|
|
|
|
.def_readwrite("move_assignments", &ConstructorStats::move_assignments)
|
|
|
|
.def_readwrite("copy_constructions", &ConstructorStats::copy_constructions)
|
|
|
|
.def_readwrite("move_constructions", &ConstructorStats::move_constructions)
|
2022-02-10 20:17:07 +00:00
|
|
|
.def_static("get",
|
|
|
|
(ConstructorStats & (*) (py::object)) & ConstructorStats::get,
|
|
|
|
py::return_value_policy::reference_internal)
|
2017-04-21 21:14:22 +00:00
|
|
|
|
2022-02-10 20:17:07 +00:00
|
|
|
// Not exactly ConstructorStats, but related: expose the internal pybind number of
|
|
|
|
// registered instances to allow instance cleanup checks (invokes a GC first)
|
2017-04-21 21:14:22 +00:00
|
|
|
.def_static("detail_reg_inst", []() {
|
|
|
|
ConstructorStats::gc();
|
|
|
|
return py::detail::get_internals().registered_instances.size();
|
2022-02-10 20:17:07 +00:00
|
|
|
});
|
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.
2016-08-07 17:05:26 +00:00
|
|
|
}
|
|
|
|
|
2022-07-08 00:51:44 +00:00
|
|
|
const char *cpp_std() {
|
|
|
|
return
|
|
|
|
#if defined(PYBIND11_CPP20)
|
|
|
|
"C++20";
|
|
|
|
#elif defined(PYBIND11_CPP17)
|
|
|
|
"C++17";
|
|
|
|
#elif defined(PYBIND11_CPP14)
|
|
|
|
"C++14";
|
|
|
|
#else
|
|
|
|
"C++11";
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
2017-04-23 23:51:44 +00:00
|
|
|
PYBIND11_MODULE(pybind11_tests, m) {
|
|
|
|
m.doc() = "pybind11 test module";
|
2015-07-05 18:05:44 +00:00
|
|
|
|
2022-07-08 00:51:44 +00:00
|
|
|
// Intentionally kept minimal to not create a maintenance chore
|
|
|
|
// ("just enough" to be conclusive).
|
|
|
|
#if defined(_MSC_FULL_VER)
|
|
|
|
m.attr("compiler_info") = "MSVC " PYBIND11_TOSTRING(_MSC_FULL_VER);
|
|
|
|
#elif defined(__VERSION__)
|
|
|
|
m.attr("compiler_info") = __VERSION__;
|
|
|
|
#else
|
|
|
|
m.attr("compiler_info") = py::none();
|
|
|
|
#endif
|
|
|
|
m.attr("cpp_std") = cpp_std();
|
|
|
|
m.attr("PYBIND11_INTERNALS_ID") = PYBIND11_INTERNALS_ID;
|
|
|
|
|
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.
2016-08-07 17:05:26 +00:00
|
|
|
bind_ConstructorStats(m);
|
|
|
|
|
2022-05-02 19:30:19 +00:00
|
|
|
#if defined(PYBIND11_DETAILED_ERROR_MESSAGES)
|
|
|
|
m.attr("detailed_error_messages_enabled") = true;
|
2017-06-08 22:44:49 +00:00
|
|
|
#else
|
2022-05-02 19:30:19 +00:00
|
|
|
m.attr("detailed_error_messages_enabled") = false;
|
2017-06-08 22:44:49 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
py::class_<UserType>(m, "UserType", "A `py::class_` type for testing")
|
|
|
|
.def(py::init<>())
|
|
|
|
.def(py::init<int>())
|
|
|
|
.def("get_value", &UserType::value, "Get value using a method")
|
Update all remaining tests to new test styles
This udpates all the remaining tests to the new test suite code and
comment styles started in #898. For the most part, the test coverage
here is unchanged, with a few minor exceptions as noted below.
- test_constants_and_functions: this adds more overload tests with
overloads with different number of arguments for more comprehensive
overload_cast testing. The test style conversion broke the overload
tests under MSVC 2015, prompting the additional tests while looking
for a workaround.
- test_eigen: this dropped the unused functions `get_cm_corners` and
`get_cm_corners_const`--these same tests were duplicates of the same
things provided (and used) via ReturnTester methods.
- test_opaque_types: this test had a hidden dependence on ExampleMandA
which is now fixed by using the global UserType which suffices for the
relevant test.
- test_methods_and_attributes: this required some additions to UserType
to make it usable as a replacement for the test's previous SimpleType:
UserType gained a value mutator, and the `value` property is not
mutable (it was previously readonly). Some overload tests were also
added to better test overload_cast (as described above).
- test_numpy_array: removed the untemplated mutate_data/mutate_data_t:
the templated versions with an empty parameter pack expand to the same
thing.
- test_stl: this was already mostly in the new style; this just tweaks
things a bit, localizing a class, and adding some missing
`// test_whatever` comments.
- test_virtual_functions: like `test_stl`, this was mostly in the new
test style already, but needed some `// test_whatever` comments.
This commit also moves the inherited virtual example code to the end
of the file, after the main set of tests (since it is less important
than the other tests, and rather length); it also got renamed to
`test_inherited_virtuals` (from `test_inheriting_repeat`) because it
tests both inherited virtual approaches, not just the repeat approach.
2017-07-25 20:47:36 +00:00
|
|
|
.def("set_value", &UserType::set, "Set value using a method")
|
|
|
|
.def_property("value", &UserType::value, &UserType::set, "Get/set value using a property")
|
2022-02-10 20:17:07 +00:00
|
|
|
.def("__repr__", [](const UserType &u) { return "UserType({})"_s.format(u.value()); });
|
2017-06-08 22:44:49 +00:00
|
|
|
|
|
|
|
py::class_<IncType, UserType>(m, "IncType")
|
|
|
|
.def(py::init<>())
|
|
|
|
.def(py::init<int>())
|
2022-02-10 20:17:07 +00:00
|
|
|
.def("__repr__", [](const IncType &u) { return "IncType({})"_s.format(u.value()); });
|
2017-06-08 22:44:49 +00:00
|
|
|
|
2022-02-08 00:23:20 +00:00
|
|
|
for (const auto &initializer : initializers()) {
|
2016-09-03 18:54:22 +00:00
|
|
|
initializer(m);
|
2022-02-08 00:23:20 +00:00
|
|
|
}
|
2015-07-05 18:05:44 +00:00
|
|
|
}
|