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
Whenever I run the standalone installer for Aptana Studio I get the following error:
Failed to Correctly Aquire installer_git_windows.exe file: CRC Error
I'm running Windows 10, I've looked online for hours and have found no solution.
I had this problem solved by installing the Git from http://go.appcelerator.com/installer_git_windows.exe.
I had the same error. I believe it still has something to do with the NodeJS.
I went to this site https://nodejs.org/en/download/ use the 32 bit version for Windows 10. Then installed an older version of Aptana https://aptana-studio.en.uptodown.com/windows/versions with the 3.4.2 and tada.. it worked. I don't mind the older version for now.
Rename the installer file to "aptana.exe"
Move that file to c drive
Open CMD in administrator mode Type "c:/aptana.exe /passive /norestart"
Press enter
After some process, a new exe file will be available on desktop which you can use.
It worked for me.
Simply download git from https://git-scm.com/download/win and install it manually before launching the Aptana installer and it will work.
I have been bogging my mind on this one for a few days with various versions of python and freeze utilities.
Python 3.6, PyQt5
I created a script, and am trying to make a standalone .exe
However, when running pyinstaller, I get the result I have posted below. I am currently using an Anaconda distribution, so I am not sure if this has anything to do with it. How do I resolve this issue?
I have tried to fix it for several days using different python and pyqt versions, but the short story is that some of the libraries I am using come into conflict in other versions. I am posting this again because nothing else has really worked, and I am on my last straws.
Thanks in advance.
Error Window:
From this page:
PyQt5 - Failed to load platform plugin "windows". Available platforms are: windows, minimal
this answer solved my problem.
Copying the folder platforms from python installation directory into my built folder solved the problem. the "platforms" folder contains qminimal.dll.
Maybe it helps you too!
Can you try to install Anaconda in a folder that does not use non-ascii characters?
Also, you say you have done conda update --all, but your Qt version states 5.6.0. Last week we released version 5.6.2, so conda update --all should have got that version for you.
Perhaps try conda update qt and see that it installs 5.6.2?
I want to install Python 2.7.12 but It shows following error.
There is a problem with this window installer package. A program required for this install to complete could not be run.
I saw one youtube video (https://www.youtube.com/watch?v=KikshWVWhzg) and so I provide full access to system and User. Even then, the same problem occurs.
How to solve this problem?
I solved this problem by my own.
Actually what happens is: In past, I installed Python 2.7.10 and by mistake, I deleted python27 file from C drive. But python remains installed in computer and when I tried to uninstall it, It shows the same error as above. So to uninstall this,
first I download similar python file (python2.7.10ci) version and try to install it. And you see it got installed. Due to this a file get generated in C drive with name python27 and now I can uninstalled python which I installed a long time back.
After uninstalling old python2.7.10, I right click on python 2.7.10ci (in control panel ) and choose repair. Due to this again a file generated with python27 and now I uninstalled this too easily.
After doing all this, I downloaded python 2.7.12 and try to install. And I able to install this without any error.
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.