[issue39393] Misleading error message upon dependent DLL resolution failure

miss-islington added the comment: New changeset 46735c7e101753769e31c69a36d0030bb056a162 by Miss Islington (bot) in branch '3.8': bpo-39393: Misleading error message on dependent DLL resolution failure (GH-18093) https://github.com/python/cpython/commit/46735c7e101753769e31c69a36d0030bb056a1

[issue39393] Misleading error message upon dependent DLL resolution failure

Steve Dower added the comment: Thanks, Zackery! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue39393] Misleading error message upon dependent DLL resolution failure

Steve Dower added the comment: New changeset 13c1c3556f2c12d0be2af890fabfbf44280b845c by Steve Dower (Zackery Spytz) in branch 'master': bpo-39393: Misleading error message on dependent DLL resolution failure (GH-18093) https://github.com/python/cpython/commit/13c1c3556f2c12d0be2af890fabfbf4

[issue39393] Misleading error message upon dependent DLL resolution failure

Change by miss-islington : -- pull_requests: +17610 pull_request: https://github.com/python/cpython/pull/18230 ___ Python tracker ___ __

[issue39393] Misleading error message upon dependent DLL resolution failure

Change by Zackery Spytz : -- keywords: +patch pull_requests: +17483 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/18093 ___ Python tracker ___

[issue39393] Misleading error message upon dependent DLL resolution failure

Eryk Sun added the comment: That clarification seems okay to me. The error message is in load_library in Modules/_ctypes/callproc.c. The underlying problem is that the directory of the DLL is only added to the search path (in CDLL.__init__ in Lib/ctypes/__init__.py) if the caller uses a qu

[issue39393] Misleading error message upon dependent DLL resolution failure

New submission from plimkilde : Under Windows with Python 3.8+, trying to load a DLL whose dependencies cannot be resolved may produce a misleading error message. For example, if we are trying to load a library foo.dll that depends on bar.dll, and bar.dll cannot be resolved while foo.dll itse