Zengtudor/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2024-11-22 05:05:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Info about inconsistent detection of Python version between pybind11 … (#1093)

Browse Source 
* Info about inconsistent detection of Python version between pybind11 and CMake in FAQ
This commit is contained in:
Semen Yesylevskyy 2018-09-12 01:20:56 +03:00 committed by Wenzel Jakob
parent f4245181ae
commit ef13fb2e1c
1 changed files with 33 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/faq.rst
View File

@ -242,6 +242,39 @@ that that were ``malloc()``-ed in another shared library, using data
structures with incompatible ABIs, and so on. pybind11 is very careful not structures with incompatible ABIs, and so on. pybind11 is very careful not
to make these types of mistakes. to make these types of mistakes.
Inconsistent detection of Python version in CMake and pybind11
==============================================================
The functions ``find_package(PythonInterp)`` and ``find_package(PythonLibs)`` provided by CMake
for Python version detection are not used by pybind11 due to unreliability and limitations that make
them unsuitable for pybind11's needs. Instead pybind provides its own, more reliable Python detection
CMake code. Conflicts can arise, however, when using pybind11 in a project that *also* uses the CMake
Python detection in a system with several Python versions installed.
This difference may cause inconsistencies and errors if *both* mechanisms are used in the same project. Consider the following
Cmake code executed in a system with Python 2.7 and 3.x installed:
.. code-block:: cmake
find_package(PythonInterp)
find_package(PythonLibs)
find_package(pybind11)
It will detect Python 2.7 and pybind11 will pick it as well.
In contrast this code:
.. code-block:: cmake
find_package(pybind11)
find_package(PythonInterp)
find_package(PythonLibs)
will detect Python 3.x for pybind11 and may crash on ``find_package(PythonLibs)`` afterwards.
It is advised to avoid using ``find_package(PythonInterp)`` and ``find_package(PythonLibs)`` from CMake and rely
on pybind11 in detecting Python version. If this is not possible CMake machinery should be called *before* including pybind11.
How to cite this project? How to cite this project?
========================= =========================
@ -256,4 +289,3 @@ discourse:
note = {https://github.com/pybind/pybind11}, note = {https://github.com/pybind/pybind11},
title = {pybind11 -- Seamless operability between C++11 and Python} title = {pybind11 -- Seamless operability between C++11 and Python}
} }