mirror of
https://github.com/pybind/pybind11.git
synced 2024-11-11 16:13:53 +00:00
Merge branch 'master' into smart_holder
This commit is contained in:
commit
c48f887cd8
@ -254,7 +254,7 @@ For instance, the following statement iterates over a Python ``dict``:
|
|||||||
|
|
||||||
.. code-block:: cpp
|
.. code-block:: cpp
|
||||||
|
|
||||||
void print_dict(py::dict dict) {
|
void print_dict(const py::dict& dict) {
|
||||||
/* Easily interact with Python types */
|
/* Easily interact with Python types */
|
||||||
for (auto item : dict)
|
for (auto item : dict)
|
||||||
std::cout << "key=" << std::string(py::str(item.first)) << ", "
|
std::cout << "key=" << std::string(py::str(item.first)) << ", "
|
||||||
@ -292,7 +292,7 @@ Such functions can also be created using pybind11:
|
|||||||
|
|
||||||
.. code-block:: cpp
|
.. code-block:: cpp
|
||||||
|
|
||||||
void generic(py::args args, py::kwargs kwargs) {
|
void generic(py::args args, const py::kwargs& kwargs) {
|
||||||
/// .. do something with args
|
/// .. do something with args
|
||||||
if (kwargs)
|
if (kwargs)
|
||||||
/// .. do something with kwargs
|
/// .. do something with kwargs
|
||||||
|
@ -390,7 +390,7 @@ operation on the C++ side:
|
|||||||
py::array b = a[py::make_tuple(0, py::ellipsis(), 0)];
|
py::array b = a[py::make_tuple(0, py::ellipsis(), 0)];
|
||||||
|
|
||||||
.. versionchanged:: 2.6
|
.. versionchanged:: 2.6
|
||||||
``py::ellipsis()`` is now also avaliable in Python 2.
|
``py::ellipsis()`` is now also available in Python 2.
|
||||||
|
|
||||||
Memory view
|
Memory view
|
||||||
===========
|
===========
|
||||||
|
@ -149,7 +149,7 @@ Your ``pyproject.toml`` file will likely look something like this:
|
|||||||
and ``pyproject.toml`` are not even contained in the wheel, so this high
|
and ``pyproject.toml`` are not even contained in the wheel, so this high
|
||||||
Pip requirement is only for source builds, and will not affect users of
|
Pip requirement is only for source builds, and will not affect users of
|
||||||
your binary wheels. If you are building SDists and wheels, then
|
your binary wheels. If you are building SDists and wheels, then
|
||||||
`pypa-build`_ is the recommended offical tool.
|
`pypa-build`_ is the recommended official tool.
|
||||||
|
|
||||||
.. _PEP 517: https://www.python.org/dev/peps/pep-0517/
|
.. _PEP 517: https://www.python.org/dev/peps/pep-0517/
|
||||||
.. _cibuildwheel: https://cibuildwheel.readthedocs.io
|
.. _cibuildwheel: https://cibuildwheel.readthedocs.io
|
||||||
@ -411,7 +411,7 @@ existing targets instead:
|
|||||||
|
|
||||||
.. code-block:: cmake
|
.. code-block:: cmake
|
||||||
|
|
||||||
cmake_minumum_required(VERSION 3.15...3.19)
|
cmake_minimum_required(VERSION 3.15...3.19)
|
||||||
project(example LANGUAGES CXX)
|
project(example LANGUAGES CXX)
|
||||||
|
|
||||||
find_package(Python COMPONENTS Interpreter Development REQUIRED)
|
find_package(Python COMPONENTS Interpreter Development REQUIRED)
|
||||||
@ -516,7 +516,7 @@ Instead of setting properties, you can set ``CMAKE_*`` variables to initialize t
|
|||||||
compiler flags are provided to ensure high quality code generation. In
|
compiler flags are provided to ensure high quality code generation. In
|
||||||
contrast to the ``pybind11_add_module()`` command, the CMake interface
|
contrast to the ``pybind11_add_module()`` command, the CMake interface
|
||||||
provides a *composable* set of targets to ensure that you retain flexibility.
|
provides a *composable* set of targets to ensure that you retain flexibility.
|
||||||
It can be expecially important to provide or set these properties; the
|
It can be especially important to provide or set these properties; the
|
||||||
:ref:`FAQ <faq:symhidden>` contains an explanation on why these are needed.
|
:ref:`FAQ <faq:symhidden>` contains an explanation on why these are needed.
|
||||||
|
|
||||||
.. versionadded:: 2.6
|
.. versionadded:: 2.6
|
||||||
|
Loading…
Reference in New Issue
Block a user