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 eryksun
Recipients Elli Pirelli, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-01-31.21:56:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485899801.31.0.736308082995.issue29399@psf.upfronthosting.co.za>
In-reply-to
Content
LoadLibraryEx with LOAD_WITH_ALTERED_SEARCH_PATH worked for me in Windows 10. I tested loading 64-bit python3.dll, for both 3.5 and 3.6, and getting the address of Py_Main. The DLLs were loaded from DLL35 and DLL36 subdirectories. It worked using both a relative and a fully-qualified path, but, per the docs, to be safe you should use the fully-qualified path to python3.dll.
History
Date User Action Args
2017-01-31 21:56:41eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, Elli Pirelli
2017-01-31 21:56:41eryksunsetmessageid: <1485899801.31.0.736308082995.issue29399@psf.upfronthosting.co.za>
2017-01-31 21:56:41eryksunlinkissue29399 messages
2017-01-31 21:56:41eryksuncreate