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 Ray Donnelly, barry, brett.cannon, eryksun, lemburg, njs, paul.moore, steve.dower, tim.golden, xoviat, zach.ware
Date 2018-01-16.20:53:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516136002.97.0.467229070634.issue32516@psf.upfronthosting.co.za>
In-reply-to
Content
I understood the proposal just fine, and I understand the problems involved and appreciate why the ideal isn't sufficient here.

The import hook was my proposal to let you only preload DLLs when the extension module is being loaded, rather than having to load all the DLLs on the first "import scipy" just in case one of its submodules gets imported later. A hook can trigger on a specific module.

Since there appears to be some uncertainty, package __init__.py always runs before its submodules are even resolved, so it's totally fine to modify import machinery or preload DLLs here. 

rpath is totally irrelevant here. The OS model is different and we've given you the available options on Windows (application directory, process-wide search path, explicit preloading, assembly probing path).
History
Date User Action Args
2018-01-16 20:53:23steve.dowersetrecipients: + steve.dower, lemburg, barry, brett.cannon, paul.moore, tim.golden, njs, zach.ware, eryksun, xoviat, Ray Donnelly
2018-01-16 20:53:22steve.dowersetmessageid: <1516136002.97.0.467229070634.issue32516@psf.upfronthosting.co.za>
2018-01-16 20:53:22steve.dowerlinkissue32516 messages
2018-01-16 20:53:22steve.dowercreate