I have a problem with my anaconda. I already installed anaconda on my windows 10, after a while, I installed WSL 2.0, now I want to add the conda to PATH. Do you know guys how can I fix it?
Not possible. Conda packages are frequently platform-specific which can mean dynamically linking against system shared libraries. Packages built for Windows will not find the appropriate libraries to run correctly within a linux-64 platform.
Rather than Anaconda, consider using a minimal base environment, like that provided by Miniconda or Miniforge. That way, you have Conda but don't install all the default Anaconda distribution packages.
Just checking if anyone knows whether Anaconda Project has released TensorFlow 2.2 and above for macOS users? From my understanding, this version of TF exists for all platforms except Mac.
Thanks for the help
you have the option to check things like this on the anaconda website. Just go to https://anaconda.org/anaconda/tensorflow and you will see:
linux-64 v2.2.0
win-64 v2.1.0
osx-64 v2.0.0
so the newest version available for macOS from the anaconda channel is (currently) 2.0.0
Alternatively you can also always run
conda search tensorflow
to see which versions are available for your platform
Note
From my understanding, this version of TF exists for all platforms except Mac
From anaconda, yes, but you are definately able to find this version on pypi, i.e. use pip install to install it
I have a anaconda installation with which I configured python 3.6, tensorflow 1.13 on windows 10. The installation works fine except when I try invoking cudnn code i.e conv2d and similar functions when I greeted with the following error: " E tensorflow/stream_executor/cuda/cuda_dnn.cc:324] Loaded runtime CuDNN library: 7.3.1 but source was compiled with: 7.4.1. CuDNN library major and minor version needs to match or have higher minor version in case of CuDNN 7.0 or later version. If using a binary install, upgrade your CuDNN library".
Which TensorFlow and CUDA version combinations are compatible?. From this post, I tried installing cudnn 7.4.1 on my desktop but looks like anaconda keeps using the default cudnn 7.3.1 only and does not reference the one pointed to by my path variables. Any help in terms of how I can force conda to use the cudnn 7.4.1 will be much appreciated.
I don't know if the original poster's problem had been resolved. Just in case someone has the same problem (as I did), one should try this first:
https://towardsdatascience.com/tensorflow-gpu-installation-made-easy-use-conda-instead-of-pip-52e5249374bc
Basically, it recommends you to directly conda tensorflow-gpu and let conda handles cudnn and cuda versions. At least afterward if you conda list it would list the updated (or more current) cudnn version.
But in my case, afterwards, I still had the same error. So I dug a little and found out it was from one of my other packages. You can search, under your anaconda folder, all occurrences of cudnn64_7.dll. For me, it's the mxnet-cu100 package that (even with the newest version) still uses the older cudnn dll. I simply copied the newer cudnn64_7.dll to that site-packages folder (with some risk I guess but at this stage, I had nothing to lose) and it solved the problem.
I want to install Julia 1.0.
I have Anaconda installed.
Information found:
In https://anaconda.org/conda-forge/julia, I see at the top of the page conda-forge / packages / julia 1.0.0. Therefore they have the latest version, released on August 8th. Below, one reads: Home: http://julialang.org/. Below the title "Installers", one reads linux-64 and osx-64. (No Windows version is mentioned). To install this package with conda run: conda install -c conda-forge julia. I am a Windows user, so I cannot install Julia 1.0 from Anaconda yet.
JuliaPro can be intalled for free from https://juliacomputing.com/products/juliapro.html.
Question:
For when they become available, what are the relative advantages of the following procedures?: (1) Install JuliaPro independently of Anaconda or (2) Install Julia 1.0 from Anaconda.
At the moment, your best bet is to download the official binary from https://julialang.org/downloads/. As far as I'm aware, the Anaconda version is more or less the same (i.e. it doesn't bundle any packages or IDE). Julia itself doesn't make use of Anaconda (it has its own package manager), so there is no real benefit to installing via Anaconda.
The new JuliaPro should be available in a few weeks, and will include a bundled IDE and pre-installed packages. Until then, you can manually install the Juno IDE yourself to work with the above build.
I have recently tried to install Python 3.4 as an alternative installation on my system in an attempt to familiarise myself before migrating code. My main Python installation is 2.7.6.
I tried the 64 bit installer for Windows, but it came up with an error message
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
After this the install is rolled back (from the point shown below):
I have eventually found a solution to this posted below and decided to share in case anyone else was having the same issue.
After some looking online I found (here) that the issue was related to conflicting pip installs (I have a version already installed for Python 2.7 and apparently this is not compatible with the version that ships with Python 3.4.
To get around this issue I simply de-selected pip from the install options shown below and the install went ahead smoothly:
Run installer again and select PIP installation.
If the PIP fails to install with the same error, you may want to check environmental variables using a tool like http://eveditor.com/ which enables to check whether they are valid. If you had another version installed before, you most likely have wrong PYTHONHOME and PYTHONPATH variables. Fix them by setting them to relevant paths. e.g. PYTHONHOME=C:\python27 and PYTHONPATH=c:\python27\Lib
You will then be able to run and install PIP.
My issue was that I had a PYTHON_HOME or PYTHON_SOMETHING environment variable set. After removing the environment variable, the installation worked perfectly.
What worked for me, strangely enough, was the "Microsoft Program Install and Uninstall troubleshooter"
The "deselect pip" solution did not work for me.
My Python 3.4.1 install was failing with the same "A program run as part of the setup did not finish as expected" error. I tried both installing it on top of Python 3.4.0 and installing it in a new folder, but got the same error. I tried uninstalling Python 3.4.0 first, but got the error during the uninstall, as well.
I ran that Microsoft utility, which helped me uninstall 3.4.0, and was then able to install 3.4.1 cleanly. The utility has options for both problematic installs and uninstalls, so it may help even if you're doing a new install, not an upgrade.
I'm running 64-bit Windows 7, but was working with 32-bit Python versions.
I had similar issues with Python 3.4x on Windows 8.1. Even after a successful install, the uninstaller would fail in the same way. Ultimately, "Method 1" at the MS forum solved this for me when I ran Microsoft's (Un)installer Fix It.
I also had the problem that pip couldn't be installed like #ChrisPosser.
So I deselected pip and the installation went fine. afterwards I restarted the setup, chose "change python" and installed pip. now everything worked like expected.
If you have any problems with windows installers I recommend activating the verbose log like this:
msiexec /i python-2.7.10-1.609.2.msi /lv install-python.log
From the logs I could see that it was the pip install, which was not working.
Yes, I faced the same issue, and was working on this for the past one hour. Was trying to uninstall the Python 3.4.1 from the control panel -> uinstall program -> add/remove program, but was facing issues.
This trick worked for me:
Manually deleted the 3.4.1 folder, which was present in my C folders after I installed the 3.4.1
Then I followed these steps:
-> Went to Regedit.exe, checked in both HKEY_CURRENT_USER, HKEY_LOCAL SOFTWARE Folder, and deleted the Python folders there.
-> windows 8 -> Downloads -> 3.4.1 msi setup (Glad I never deleted it)
-> Right clicked on the msi setup and choose the repair option
-> The repair would re install the Python 3.4.1
-> After this, I un-installed the Python 3.4.1
-> Then I deleted the 3.4.1 msi setup.
Rebooted the system, and now, there is no instance of Python 3.4.1 in my system.
According to me when environment variables containing name 'Python' are created they somehow becomes related with python. I was unable to open idle (GUI PUTHON) and to uninstall it . Deleting a variable named 'PYTHON PATH' solved my all python related problems.
I had 3.7.4 and wanted to move to 2.7.13.
I uninstalled 3.7.4
Tried to install 2.7.13 but got the same error.
There was a 2.7.10 installer(not msi) also present, uninstalling which gave the same error.
So I downloaded 2.7.10 msi, installed it, and then just installed 2.7.13 from the downloaded msi and it worked fine. This overwriting worked because the major version i.e. 2.7 was same for both.
I don't know if this is helpful but after the hours I spent on this, I wanted to write out what worked for me.
Yup, I have already installed another version of python. I have uninstalled them using Program features. But still the same issue persisted because of the folder which was present in my C: drive. After deleting them manually, the installation got completed without errors
I faced this issue because of 2 conflicting versions of 7zip. Removing them both and installing just one fixed this issue.
I had python3.4 installed, then added 3.5, and deleted 3.4. That was a mistake. In trying to get a library to work, I had to go back to 3.4. I uninstalled 3.5, but couldn't uninstall 3.4 (folder deleted).
I ended up searching the registry in rededt32 for "python". There was a Guid folder with a number of entries that had c:\python34 and one more related to the same folder that I deleted. After this, the install worked correctly.
Windows 10.
Mine was linked to having installed an older version in the past, only for my own user account. I got around it by telling the installer to install Python for all users.
For me none of the suggested fixes worked for me. However checking the option "Install just for me" instead of "Install for all users" (Windows 10) worked for me. So this might be another option to try.