Good day, I'm having some hard to debug error likely related to shared pointers but I don't even know if it is a boost python issue or outdated configuration. I'm using boost 1.72 and msvc 2017 (15.9.7). What I noticed is that when I build on Linux (devtoolset 6), execution reaches further -fails in the end but checking with the debugger things seemed good even past the point I fail on Windows.
Linux seems to enable the define BOOST_PYTHON_TYPE_ID_NAME, and this changes how the existence of valid converters is tested. On Linux an (existing) converter is found because it takes the path of that define. On Windows, the existing converter is reported as not. I tried to add the define to the command line and the build passed. But execution failed when loading the c++ extension into python with an assert during one of the registers: "slot->m_to_python == 0". So, before I go on a useless hunt, should BOOST_PYTHON_TYPE_ID_NAME (or lack of) work on Windows?
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org https://mail.python.org/mailman/listinfo/cplusplus-sig
