indygreg / indygreg/PyOxidizer
pyzmq cython backend DLL failure
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Version information: Windows 10, PyOxidizer 0.10.3 with cargo.
On a conda environment with zeromq and pyzmq installed, running `pyoxidizer run` the import of `zmq.backend.cython` fails with DLL load error.
```
adding extra file python38.dll to precert
installing files to C:\Users\user\dev\pyapp\.\build\x86_64-pc-windows-msvc\debug\install
Traceback (most recent call last):
File "runpy", line 194, in _run_module_as_main
File "runpy", line 87, in _run_code
File "pyapp.main", line 13, in
File "zmq", line 55, in
File "zmq.backend", line 40, in
File "zmq.utils.sixcerpt", line 34, in reraise
File "zmq.backend", line 27, in
File "zmq.backend.select", line 28, in select_backend
File "zmq.backend.cython", line 6, in
ImportError: DLL load failed while importing error: The specified module could not be found.
error: cargo run failed
```
I guess this is because the zeromq installation can't be found from within pyzmq in the PyOxidizer context. I read the Packaging User Guide, but could not figure out how PyOxidizer solves these situations internally - or how the user is supposed to resolve this. Any further pointers or am I missing something else? I found #107, but I see my starting point from https://github.com/indygreg/PyOxidizer/issues/107#issuecomment-516267303 where zeromq and pyzmq is already installed in the environment.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported `pyoxidizer run` failure on Windows 10 with the stated conda, PyOxidizer, zeromq, and pyzmq setup. Trace the import of `zmq.backend.cython` and the missing DLL from the displayed traceback, then compare the behavior with the Packaging User Guide and issue #107. Done means the cause and a supported resolution for this packaged application are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100