Author eryksun
Recipients eric.snow, eryksun, jkloth, lukasz.langa, mattip, ncoghlan, pablogsal, paul.moore, ralf.gommers, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-03-30.19:59:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553975975.47.0.69294307874.issue36085@roundup.psfhosted.org>
In-reply-to
Content
WinDLL('./_sqlite3.dll') succeeds, which just delays the call to GetFullPathNameW to the CDLL constructor, so I don't see how the working directory is a factor. The difference I see is the lack of the LOAD_LIBRARY_SEARCH_DEFAULT_DIRS flag. Try including the individual flags (i.e. LOAD_LIBRARY_SEARCH_SYSTEM32, LOAD_LIBRARY_SEARCH_APPLICATION_DIR, LOAD_LIBRARY_SEARCH_USER_DIRS) one by one until it works.

We could enable loader snaps in the registry for the Python executable; run it as a debugger; and log the debug output to see exactly what the loader is failing to find and where it's searching.
History
Date User Action Args
2019-03-30 19:59:35eryksunsetrecipients: + eryksun, paul.moore, ncoghlan, vstinner, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, mattip, steve.dower, ralf.gommers, pablogsal
2019-03-30 19:59:35eryksunsetmessageid: <1553975975.47.0.69294307874.issue36085@roundup.psfhosted.org>
2019-03-30 19:59:35eryksunlinkissue36085 messages
2019-03-30 19:59:35eryksuncreate