unstable Python interpreter version? about kadas-albireo2 HOT 3 CLOSED

Encountered a problem along a similar line:

In the Kadas /bin directory the Python dll is named libpython3.9.dll instead of python39.dll (in official Python release). For Valhalla's bindings that's a problem, boost-python needs python39.dll which it is built against. Confirmed by renaming the dll while QGIS was open, then I could import Valhalla's bindings.

Is it possible for Kadas to stick to the more standard python39.dll?

from kadas-albireo2.

As KADAS is compiled using the MinGW toolchain and not MSVC, the naming convention used when building python via GNU Makefiles is used throughout. Briefly looking into it, I don't think it's practicable renaming the library without causing lots of breakage within python itself.

We will be following up with 2.0.2 shortly which will bring python3.9 final (or worst case rc2).

from kadas-albireo2.

Thanks for the info. Either we'll try to compile valhalla with MinGW or try to switch to pybind11 which shouldn't have the same issues.

from kadas-albireo2.