Message377322
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. |
|
Date |
User |
Action |
Args |
2020-09-22 14:04:23 | pombredanne | set | recipients:
+ pombredanne |
2020-09-22 14:04:23 | pombredanne | set | messageid: <1600783463.67.0.783578166669.issue41836@roundup.psfhosted.org> |
2020-09-22 14:04:23 | pombredanne | link | issue41836 messages |
2020-09-22 14:04:23 | pombredanne | create | |
|