New submission from plimkilde <peter.limki...@gmail.com>:
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 itself can, Python gives this error message: "FileNotFoundError: Could not find module 'foo.dll'. Try using the full path with constructor syntax." (behavior introduced with PR #12302) Personally, I'd be happy to see a fix that simply adds " (or one of its dependencies)" to the error message. ---------- components: Windows, ctypes messages: 360305 nosy: paul.moore, plimkilde, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Misleading error message upon dependent DLL resolution failure type: behavior versions: Python 3.8, Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue39393> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
