Issue41836
Created on 2020-09-22 14:04 by pombredanne, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg377322 - (view) | Author: Philippe Ombredanne (pombredanne) * | Date: 2020-09-22 14:04 | |
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. |
|||
| msg377324 - (view) | Author: Eric V. Smith (eric.smith) *  |
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". |
|||
| msg377325 - (view) | Author: Philippe Ombredanne (pombredanne) * | Date: 2020-09-22 14:16 | |
Eric, Thanks! This is IMHO a dupe of https://bugs.python.org/issue25655 in earnest. So I am closing this in favor of that and will carry over comments there |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:35 | admin | set | github: 86002 |
| 2020-09-22 14:16:25 | pombredanne | set | status: open -> closed messages: + msg377325 components:
- Windows |
| 2020-09-22 14:13:47 | eric.smith | set | nosy:
+ eric.smith, zach.ware, paul.moore, tim.golden, steve.dower messages: + msg377324 components: + Windows |
| 2020-09-22 14:08:16 | The Compiler | set | nosy:
+ The Compiler |
| 2020-09-22 14:07:53 | altendky | set | nosy:
+ altendky |
| 2020-09-22 14:04:23 | pombredanne | create | |