[issue41836] Improve ctypes error reporting with missing DLL path

Philippe Ombredanne added the comment: 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 -- components: -Windows resolution: -> duplicate stage: -> resolved status: open ->

[issue41836] Improve ctypes error reporting with missing DLL path

Eric V. Smith added the comment: 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". -- components: +Windows nosy: +eric.smith, paul.moore, steve.dower,

[issue41836] Improve ctypes error reporting with missing DLL path

Change by Florian Bruhin : -- nosy: +The Compiler ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41836] Improve ctypes error reporting with missing DLL path

Change by Kyle Altendorf : -- nosy: +altendky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41836] Improve ctypes error reporting with missing DLL path

New submission from Philippe Ombredanne : 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