I just installed Anaconda3 (64-bit) Individual Edition on my Windows 7 machine. I was instructed to do this by setup instructions for an upcoming workshop I'm attending; they said, "Installing all of Python's research packages individually can be a bit difficult, so we recommend Anaconda, an all-in-one installer."
Is it possible to install another Python IDE, such as IDLE, on the same computer as Anaconda?
Definitely yes.
My pc is also running at 64 bits and windows 7.
I have Anaconda (Spyder as editor) and IDLE (interactive shell) at the same time.
Having Anaconda is useful in sense that lots of packages of modules were included when we install it.
I don't know if I got your question right, but I have Anaconda on my computer + PyCharm, I didn't face trouble
Yes, this is possible, but i think Anaconda is going to override the packages installed from python installer.
I downloaded Anaconda 5.3 and am trying to Install RStudio in it. I get the below error always after upgrading.
"Some of the functionality of Anaconda Navigator will be limited in offline mode."
"Installation and upgrade of packages will be subject to the packages currently available on your package cache."
Even if the internet is connected, I get the same error which didnt happen with previous version. Does anyone know how to overcome this? Please advise.
Btw, RCran and RStudio are not approved software and hence I am trying to use the one through Anaconda IDE.
Same as you here, there is an issue related https://github.com/ContinuumIO/anaconda-issues/issues/10176.
While anaconda-navigator having this problem, you can still install packages through anaconda prompt.
open anaconda prompt in your start menu
type conda install rstudio
I have been using Mayavi under enthought Canopy successfully for past 8 months. During a recent update using egg, I got a message about a missing egg in the Canopy package manager and found Mayavi Hanging. I tried to revet to older Mayavi (4.0.0) but no luck. It only works if I revert to Mayavi 3.4 version.
Can somebody suggest me possible sources of error. I am using Windows 8 64bit. Running Mayavi2.exe, Mayavi-script2.py and importing mayavi - none of these work under Mayavi version 4.0.0 onwards. ( On a 32 bit machine, however, I have no problems)
I suggest that you reset your Canopy User Python environment to start clean:
In the Canopy GUI, print sys.prefix to see where that environment's directory is, then quit Canopy and delete that directory (e.g. in Windows Explorer). Restart Canopy, and your environment will be auto-recreated from the installation-time eggs. (For that reason, you might want to first take the time to uninstall your Canopy, and install the current Canopy 1.5.1 from https://store.enthought.com/downloads/ but that's secondary) -- in-app auto-updates are currently disabled, and will be for at least a few more weeks.
Then open a Canopy Command Prompt (from the Start Menu or from the Canopy Tools menu) and type
enpkg mayavi to update to the current mayavi.
If you are non-academic free user, you'll need to wait a few days before this will work, as Mayavi is not currently accessible to such users using enpkg. Sorry for that inconvenience.
After uninstalling and re-installing Mayavi a couple of times, I continued to have the same problem that Mayavi used to hang.
I have managed to solve it by deleting a file
C:\Users\SUK000???\AppData\Roaming\Enthought\mayavi_e3\pyface\workbench\wx\windows_memento
It seems that Mayavi creates this file by default if it does not exist. If it exists, it tries to use the settings in this file to open Mayavi interface and hangs if it does not like the settings.
That was a relief. Thanks for your ideas.
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.
I installed Enthought Canopy onto my 64 bit windows box (Windows 7).
Installed "successfully" except Canopy would not run at all from start menu. I tried running it from cmd and it still would not run.
I checked c:\Users\user...Local and Roaming and found no error logs.
I tried the Windows Vista and above with User Access Control (UAC) enabled, the msi installer trick but Canopy still didn't run either from start menu or cmd.
There seems no help on this on the Enthought website, has anyone else seen and solved the problem?
Maybe too late as you may already have saolved your problem. But I get the same problem after installing.
Did you install a standalone version of python and have a PYTHONPATH variable already defined?
By me, I just remove the PYTHONPATH variable and then Canopy starts correctly