Is it good practice to have all DLLs in local directories, sure it is. Who installed what, probably can only be found by a dependency walker. Out of the 70,000 DLLs on my small test system around 4000 DLLs are in System32. These libraries are around since many years dating back to 1994. This is an issue with I agree.īut reality is that Microsoft and many other vendors ship these DLLs as part of different packages and they are sometimes installed in System32 and sometimes not. To very old versions ranging from 2009 to 2017. Basically the libraries that are loaded refer Basically the Anaconda Navigator or Spyder or python installed through different environments do not load the correct DLL versions.Ĭ:\Anaconda3\Library\bin\mkl_intel_thread.dll (october 2016)Ĭ:\Anaconda3\pkgs\mkl-2017.0.3-0\Library\bin\mkl_intel_thread.dll (april 2017)Ĭ:\Anaconda3\pkgs\mkl-2017.0.3-0\Library\bin\mkl_core.dll (april 2017)Ĭ:\Anaconda3\Library\bin\mkl_core.dll (october 2016)Ĭ:\Anaconda3\pkgs\mkl-2017.0.3-0\Library\bin\libiomp5md.dllĬ:\Anaconda3\envs\tensorflow-cpu\Library\bin\libiomp5md.dllĬ:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32\compiler\libiomp5md.dllĬ:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler\libiomp5md.dllĮach of them different versions, file sizes and versions. Now the problem is, that there are multiple versions for each of the DLLs (DLL hell)Īll different dates, versions, file sizes. Some further investigation (only based on numpy and python 3.6.2 leads toĬ:\Anaconda3\envs\tensorflow-cpu\Lib\site-packages\numpy\core\multiarray.cp36-win_amd64.pydĬ:\Windows\System32\mkl_intel_thread.dll (v2009)Ĭ:\Windows\System32\libiomp5md.dll (v2009) This worked fine with an old install of Anaconda3-4.3.1-Windows-x86_64.exe for a couple of weeks,Ī new install after everything was broken based on update/upgrade procedures gives the same errors. Original error was: DLL load failed: The specified procedure could not be found. ImportError: DLL load failed: The specified procedure could not be found.ĭuring handling of the above exception, another exception occurred:įile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy_ init_.py", line 142, inįile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy\add_newdocs.py", line 13, inįile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy\lib_ init_.py", line 8, inįile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy\lib\type_check.py", line 11, inįile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy\core_ init.py", line 26, in Type "help", "copyright", "credits" or "license" for more information.įile "C:\Anaconda3\envs\tensorflow-cpu\lib\site-packages\numpy\core_ init_.py", line 16, in Otherwise reinstall numpy.Īnother error just for conda Numpy WIN 64-bit v1.13.1. If you're working with a numpy git repo, try git clean -xdf (removes allįiles not under version control). Likely you are trying to import a failed build of numpy. Importing the multiarray numpy extension module failed. (worked for couple of month before, really liked it). Numpy WIN 64-bit v1.13.1 just worked fine in Anaconda navigator and Spyder, but since July 2017Īnd some weird updates, NUMPY under Windows and Python 3.6.1 does not work anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |