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 mattip
Recipients brett.cannon, eric.snow, eryksun, jkloth, mattip, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-23.16:57:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Clear documentation would go a long way toward onboarding package providers. Of course this does not solve the problem for packages with no active ongoing support for windows, and will annoy developers whose code base is full of `os.environ['PATH']` games. Perhaps the solution should come with a deprecation warning when setting `os.environ['PATH']`.

It would be very helpful if failure to import a pyd (or for that matter to open a DLL with ctypes) due to missing support dlls could be easily debugged. Right now we get a message from windows that seems to suggest the file was not found.
- Python could check if the file exists on disk and print a more helpful message
- A debug hook to print the dll search path at the time of the failed LoadLibraryEx call, or perhaps adding it as an attribute of the Exception (this might be nice to have on Linux as well, even though there the Exception already includes the name of the missing *.so).

Even better would be official python/Microsoft support for a CLI version of depends.exe like ldd on linux, but that seems much harder and is out of scope for this issue.
Date User Action Args
2019-02-23 16:57:47mattipsetrecipients: + mattip, brett.cannon, paul.moore, ncoghlan, tim.golden, jkloth, eric.snow, zach.ware, eryksun, steve.dower
2019-02-23 16:57:47mattipsetmessageid: <>
2019-02-23 16:57:47mattiplinkissue36085 messages
2019-02-23 16:57:47mattipcreate