Author mattip
Recipients brett.cannon, eric.snow, eryksun, jkloth, lukasz.langa, mattip, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-03-12.07:12:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552374744.41.0.952719724516.issue36085@roundup.psfhosted.org>
In-reply-to
Content
Correct me if I'm wrong, but once SetDefaultDllDirectories() is used, there is no going back: PATH no longer can change the search path no matter what flags are used with LoadLibrary* calls (see the recent Anaconda issue when they did this and broke NumPy). Assuming that is true, then

> add sys._adddlldirectory() and sys._removedlldirectory() as CPython-specific functions for extending the search path (for use by packages currently modifying PATH at runtime)

Why is this CPython-specific and "private"? It seems like
* it should be a public interface, used by all implementations consistently, as a policy decision for the win32 platform and documented as such
* located in os, much like os.environ (not critical)

There should be some kind of debugging tool for when LoadLibraryEx fails, to indicate what might have gone wrong, perhaps os.getdlldirectory() would be helpful
History
Date User Action Args
2019-03-12 07:12:24mattipsetrecipients: + mattip, brett.cannon, paul.moore, ncoghlan, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, eryksun, steve.dower
2019-03-12 07:12:24mattipsetmessageid: <1552374744.41.0.952719724516.issue36085@roundup.psfhosted.org>
2019-03-12 07:12:24mattiplinkissue36085 messages
2019-03-12 07:12:24mattipcreate