Miniconda from Chocolatey has DLL fail for PyQt5

[native-api]

Use dumpbin, Dependencies or Process Monitor. The last one is the most (the only?) reliable way but is a bit complicated.

Failing to run compiled Python extension

tests\py\testsuite.py:3: in <module> from .numericaltests import NumericalDataUnitTest tests\py\numericaltests.py:4: in <module> import peakingduck as pkd peakingduck\__init__.py:1: in <module> import peakingduck.util as util peakingduck\util\__init__.py:2: in <module> from PEAKINGDUCK.util import * E ImportError: DLL load failed while importing PEAKINGDUCK: The specified module could not be found. Is the last name intended to be in CAPS? Other than that, “The specified modu…

Failing to run compiled Python extension

dumpbin is not on PATH, use info on the provided links or find /c to locate it. Others are not present, you need to download them yourself. I deliberately didn’t mention depends among the links because it’s obsolete (doesn’t support API sets), use Dependencies instead. Whether something is “wrong” or not, only one way to find out.

Failing to run compiled Python extension

Bottom line: change compiler flags to link to libgcc and libstdc++ statically. Or place them (with any transitive MinGW-specific dependencies) alongside the .pyd and distribute with your module. I’ve diagnosed the problem with Process Monitor using the following code. This is the most reliable way because you get to see what the system is actually searching for, and where, rather than look at metadata and make assumptions. Since Windows’ DLL search process is compilcated and very settings-de…