Miniconda from Chocolatey has DLL fail for PyQt5

[djhoese]

I’ve been testing this for at least a week now and have finally gotten to the point that I don’t think there is much more that I can do. This only seems to be a problem with Travis and only with Windows, but could be a problem specifically with Chocolatey or I’m just missing some small thing to get it to work.

I have stripped down my environment to the simplest form that I can think of so it:

1. Installs miniconda
2. Does “conda init” and resources .bash_profile.
3. Creates a new environment with pyqt installed in a Python 3.7 environment.
4. Try python -c "from PyQt5.QtWebEngineWidgets import QWebEngineView" and it fails with:

Traceback (most recent call last):

  File "<string>", line 1, in <module>

ImportError: DLL load failed: The specified module could not be found.

Here is the build: https://travis-ci.org/github/ssec/sift/builds/661182075

I have almost no experience tracking down DLL issues on Windows so any help would be very appreciated. Note that this works fine on a real Windows machine with Miniconda installed directly. I don’t have a Windows box with Chocolatey available to me right now.

Edit: Also note I’ve tried this with conda-forge packages which include PyQt 5.12 and I’ve tried installing PyQt from PyPI (via pip) in to an environment with just Python 3.7 and that has the same issue.

[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…

[djhoese]

Thanks for the information. I first tried dependencies but that list was long and hard to tell what was the problem. I then followed your example of using procmon from the other thread and loaded it in a local Windows VM. It looks like the main issue is PyQt trying to load DirectX since our tests are on a GUI application. Based on what I’ve found here DirectX isn’t currently supported, right?

[native-api]

Yes, multimedia functionality is currently not supported.
You may want to vote on this feature request:

Make running GUI/multimedia apps available in Windows

Trying to run some GUI tests(conda/pyqt5/pytest) inside Windows build, but apparently GUI isn’t supported on Windows Server Core. Is there any change to have GUI enabled images in the future? Or maybe I am missing something.