Windows binary of boost_python3 built against incorrect headers

[John Soklaski]

I believe the windows binaries for boost_python3 are being built against the python 2 headers.

When I dump the exports from the latest lib:

dumpbin /exports "C:\local\boost_1_65_0_beta1_rc2\lib64-msvc-14.0\boost_python3-vc140-mt-1_65.lib"  | find /i "init_module"
                  ?init_module@detail@python@boost@@YAPEAU_object@@PEBDP6AXXZ@Z (struct _object * __cdecl boost::python::detail::init_module(char const *,void (__cdecl*)(void)))

From the lib I've built myself:

dumpbin /exports "C:\local\boost_1_64_0\stage\lib\boost_python3-vc141-mt-1_64.lib" | find /i "init_module"
                  ?init_module@detail@python@boost@@YAPEAU_object@@AEAUPyModuleDef@@P6AXXZ@Z (struct _object * __cdecl boost::python::detail::init_module(struct PyModuleDef &,void (__cdecl*)(void)))

The signature of init_module is determined this #ifdef (from http://www.boost.org/doc/libs/1_64_0/boost/python/module_init.hpp):

#  if PY_VERSION_HEX >= 0x03000000

BOOST_PYTHON_DECL PyObject* init_module(PyModuleDef&, void(*)());

#else

BOOST_PYTHON_DECL PyObject* init_module(char const* name, void(*)());

#endif

Based on this code, the boost_python3 library appears to be built against the python 2 headers.

[Thibaud de Souza]

I observe the same. Is there a specific reason not to fix this, or at least acknowledge that there is an issue here?

[sl se]