➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pombredanne
Recipients The Compiler, never-eat-yellow-snow, paul.moore, pombredanne, steve.dower, tim.golden, zach.ware
Date 2020-09-22.14:18:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1600784336.97.0.610943418119.issue25655@roundup.psfhosted.org>
In-reply-to
Content 
From https://bugs.python.org/issue41836 closed as a dupe of this:

When the dependency of a DLL is missing (at least on Windows) the error " OSError: [WinError 126] The specified module could not be found" is raised when calling ctypes.CDLL(dll_path) even when this "dll_path" exists... because the error comes from another DLL.

These errors are really hard to diagnose because the path of the missing DLL is not returned in the exception message. Returning it would help fixing these kind of errors quickly.

Researching errors such as this one https://github.com/nexB/scancode-toolkit/issues/2236 wastes quite a bit of time and would be made a non issue if we had the path in the error message.


and this reply from Eric Smith: https://bugs.python.org/msg377324

> Author: Eric V. Smith (eric.smith) * (Python committer) 	Date: 2020-09-22 14:13

> My understanding is that Windows doesn't tell you which DLL is missing. I think the best we could do is append something to the error message saying "or one its dependencies".
History
Date User Action Args
2020-09-22 14:18:57pombredannesetrecipients: + pombredanne, paul.moore, tim.golden, zach.ware, steve.dower, The Compiler, never-eat-yellow-snow
2020-09-22 14:18:56pombredannesetmessageid: <1600784336.97.0.610943418119.issue25655@roundup.psfhosted.org>
2020-09-22 14:18:56pombredannelinkissue25655 messages
2020-09-22 14:18:56pombredannecreate