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 plimkilde
Recipients paul.moore, plimkilde, steve.dower, tim.golden, zach.ware
Date 2020-01-20.09:27:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579512450.11.0.864670825995.issue39393@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2020-01-20 09:27:30plimkildesetrecipients: + plimkilde, paul.moore, tim.golden, zach.ware, steve.dower
2020-01-20 09:27:30plimkildesetmessageid: <1579512450.11.0.864670825995.issue39393@roundup.psfhosted.org>
2020-01-20 09:27:30plimkildelinkissue39393 messages
2020-01-20 09:27:29plimkildecreate