➜

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 steve.dower
Recipients brett.cannon, eric.snow, eryksun, jkloth, lukasz.langa, mattip, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-03-12.15:45:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552405521.1.0.0491360072525.issue36085@roundup.psfhosted.org>
In-reply-to
Content 
Since I just dug enough to find it, the best way to diagnose problems with dependent DLLs not being found is probably to run Process Monitor [1] while doing the import and checking its logs. It should show the paths that were attempted to be accessed.

[1]: http://technet.microsoft.com/en-us/sysinternals/bb896645
History
Date User Action Args
2019-03-12 15:45:21steve.dowersetrecipients: + steve.dower, brett.cannon, paul.moore, ncoghlan, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, mattip, eryksun
2019-03-12 15:45:21steve.dowersetmessageid: <1552405521.1.0.0491360072525.issue36085@roundup.psfhosted.org>
2019-03-12 15:45:21steve.dowerlinkissue36085 messages
2019-03-12 15:45:21steve.dowercreate