[issue35688] "pip install --user numpy" fails on Python from the Windows Store

mattip added the comment: I think the original problem we had with the AddDllDirectory approach was that once set, it seems to mitigate searching the os.environ['PATH'] for dll loading. Is that accurate? Would RemoveDllDirectory restore the ability to find DLLs along the system PATH? >

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Eryk Sun added the comment: > I didn't realize assemblyBinding was supported by the generic runtime > framework, the documentation https://docs.microsoft.com/en-us/dotnet/ > framework/deployment/how-the-runtime-locates-assemblies seems to > suggest it is a dotnet feature. Native private

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

mattip added the comment: @eryksun thanks for the details. I didn't realize assemblyBinding was supported by the generic runtime framework, the documentation https://docs.microsoft.com/en-us/dotnet/framework/deployment/how-the-runtime-locates-assemblies seems to suggest it is a dotnet

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Eryk Sun added the comment: It may suit the needs of NumPy and SciPy to use an assembly for DLL dependencies. With an assembly it's possible for two DLLs with the same name to load in a process and possible for a DLL to extend the assembly search path with up to nine relative paths at load

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

mattip added the comment: Closing. It seems the days of modifying os.environ['PATH'] on windows are over, and packages need to adopt to calling AddDllDirectory. As long as python is built with ctypes, this is easy enough to adopt, even though there are some caveats. See the issue from

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Steve Dower added the comment: > use AddDllDirectory, (which is as accessable as os.environ['PATH'] but is not > considered a security risk so far) The parenthical is incorrect. The user-specified DLL search directory is separate from PATH, and both appear in the default DLL search order

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

mattip added the comment: 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

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Steve Dower added the comment: I posted on the numpy thread: Most likely the DLL is failing to load, which the importer returns as "not found" (as it falls back on other search mechanisms and doesn't retain the error). I suggested loading it directly with ctypes to see if there's a better

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

mattip added the comment: The difference in search order between apps from the app store and desktop applications may be relevant https://docs.microsoft.com/en-us/windows/desktop/Dlls/dynamic-link-library-search-order#alternate-search-order-for-windows-store-apps --

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Change by Stephan Troyer : -- nosy: +stephtr ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35688] "pip install --user numpy" fails on Python from the Windows Store

Change by Karthikeyan Singaravelan : -- title: "pip install --user numpy" fails on Python from the Windos Store -> "pip install --user numpy" fails on Python from the Windows Store ___ Python tracker