You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think I can replicate this in a simple case, but I have two modules, each that operate just fine when they are the only module imported.
Builds are inside a conda environment, with visual studio 2015 64-bit as compiler. One package is this one: https://github.com/usnistgov/CEGO and the other one is an internal C++ library with a pybind11 wrapper.
When they are both imported, like so:
importPyCEGOimportVLEIsoTracerasvle
I get a crash:
The text was updated successfully, but these errors were encountered:
It seems like one library was built with commit 2bde615 and the other one was built with 51d18aa . When I sync both to master, there is no import crash. It seems like a bug that any modules compiled with pybind11 with two different commits result in a crash.
This was improved/fixed in #1012.
Meanwhile, the two commits you mention were not official releases, so you're it's not really a surprise that things don't cooperate well, then.
I don't think I can replicate this in a simple case, but I have two modules, each that operate just fine when they are the only module imported.
Builds are inside a conda environment, with visual studio 2015 64-bit as compiler. One package is this one: https://github.com/usnistgov/CEGO and the other one is an internal C++ library with a pybind11 wrapper.
When they are both imported, like so:
I get a crash:
The text was updated successfully, but these errors were encountered: