Message 333732 - Python tracker

Message333732

Author mattip
Recipients brett.cannon, mattip, paul.moore, stephtr, steve.dower, tim.golden, zach.ware
Date 2019-01-15.21:44:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1547588682.76.0.813242762065.issue35688@roundup.psfhosted.org>
In-reply-to
Content
It seems changing os.environ['PATH'] is a security risk and is not allowed for Windows Store apps. The suggestion in the NumPy issue is to:

- use AddDllDirectory, (which is as accessable as os.environ['PATH'] but is not considered a security risk so far), but this requires using SetDefaultDllDirectories which breaks other things

- put any dlls required for the c-extension pyd in the same directory which means scipy and numpy will be using duplicate and potentially different OpenBLAS dlls, and whoever imports first wins

- load all the required dlls via LoadLibrary, meaning NumPy will have to export a windows-only API to SciPy so the latter can know where the DLL is.

I am glad NumPy only has one DLL, and not a dozen like QT or wxPython. 

Is there a PEP that describes the overall design of windows directory layout or a design guide for package authors with best practices for additional dll dependencies?
History
Date User Action Args
2019-01-15 21:44:44mattipsetrecipients: + mattip, brett.cannon, paul.moore, tim.golden, zach.ware, steve.dower, stephtr
2019-01-15 21:44:42mattipsetmessageid: <1547588682.76.0.813242762065.issue35688@roundup.psfhosted.org>
2019-01-15 21:44:42mattiplinkissue35688 messages
2019-01-15 21:44:42mattipcreate