Could not find module libdelaunator.dll about dhmqc HOT 5 CLOSED

Appears to be caused by this change introduced in Python 3.8:

DLL dependencies for extension modules and DLLs loaded with ctypes on Windows are now resolved more securely. Only the system paths, the directory containing the DLL or PYD file, and directories added with add_dll_directory() are searched for load-time dependencies. Specifically, PATH and the current working directory are no longer used, and modifications to these will no longer have any effect on normal DLL resolution. If your application relies on these mechanisms, you should check for add_dll_directory() and if it exists, use it to add your DLLs directory while loading your library. Note that Windows 7 users will need to ensure that Windows Update KB2533623 has been installed (this is also verified by the installer). (Contributed by Steve Dower in bpo-36085.)

from dhmqc.

Strangely enough, this only seems to affect libdelaunator.dll, not the other DLLs in that directory.

from dhmqc.

Sigh... This error seems to be another case of misleading "missing DLL" messages on Windows.

Unlike the other DLLs in its directory, libdelaunator.dll currently has dependencies on DLLs for MinGW's C and C++ standard libraries.

The error message masks the actual error, which is failure to resolve those MinGW DLLs (on my machine, libgcc_s_seh-1.dll and libstdc++-6.dll) under Python 3.8's stricter rules.

As a workaround for now, DHMQC can be installed in an Conda environment with Python pinned to 3.7 (add python=3.7 to the packages to install).

from dhmqc.

Behaviour regarding the misleading error message reported to Python's issue tracker here: https://bugs.python.org/issue39393

from dhmqc.

It seems only Python 3.8 (and not 3.9+) is fussy about DLL paths here, so I'm going to take the easy way out and support only 3.9 and 3.10 😄

from dhmqc.