Anaconda 64bit install has begun to fail - python-3.x

I have been using Anaconda 3-5.0.1 with spyder3. Spyder has begun to fail.
I tried to remove and reinstall but reinstall fails. I removed hidden folder
anaconda3 to no avail. I now have no working spyder. I am installing 64-bit version in Windows 10. There are a variety of error messages including cant create menus. I have run this install many times prior to today (2/8/2018).
I assume continuum changed something.
I would greatly appreciate guidance.

For those of you who still have the same issue, try to follow the link below.
http://shirabeta.net/Anaconda-install-error.html#.WopGl6huY2z
You may need to have a google translate as it's a Japanese blog.
I deleted JDK, JRE and all java related paths in the environment setting as suggested in the blog. Then I could successfully install anaconda3.5.1.0_64bit with no error.

Related

Python, Anaconda & PyCharm multiple versions of Python3

I just installed Anaconda3-2019-10 on my MacBook.
I tried to make sure that my previous Python 3 version was totally uninstalled / removed from my system. Typing python3to the terminal didn´t work anymore.
After installing Anaconda and PyCharm (pycharm-community-anaconda-2019.3.3) I started a new Project to test everything. For that I selected to create a new Conda environment:
After I created the process I checked the Preferences and the "Project Interpreter". This is what I found:
I expected to find two interpreters 1.) my 3.7 Python version and 2.) the Conda environment just created.
Does finding 3 versions mean that I didn´t correctly deinstall Python3 before installing anaconda or is there anything that I don´t understand here?
Do I need both versions?
If not is there a safe way to remove one of them?
For removing Python3 from my system I did almost everythin suggested in numerous posts in Stackoverflow.
Upon creating a venv(virtual environment) you no longer need to worry about the existing interpreter. https://docs.python.org/3/tutorial/venv.html this might be of help.

Aptana 3 (3.6.1) Will Not Load on my Windows 10 Laptop

I know you all heard similar complaints, yet no response has worked for me through browsing these questions and answers. Please forgive me if you believe this to overly repetitive.
Loaded Node.js (4.2.2) first tried 32bit, and later tried 64bit installer.
Attempted to load Aptana studio 3 (3.6.1) but got an error.
"Failed to acquire installer_nodejs_windows.msi file: CRC error."
I have tried updating environmental variables, and loading the 64bit instead. I have uninstalled, reinstalled, rebooted, etc. I like this application on my school computer, and really want to give it a try at home. Can someone please help me?
I am also using windows 10 and encountered same error. Download and Install the file http://go.aptana.com/installer_nodejs_windows manually and then run aptana installer. It will work.
Same error. Install Node js
Install Node JS:
https://nodejs.org/en/download/

I stopped the installation of package abruptly in sdk manager in Linux. Thereafter the window does not open

I am using Android Studio in Ubuntu 14.4 lts. While installing certain packages through Sdk Manager, i stopped them, as i realized i didn't need them. After which i could not open the sdk manager altogether.
I tried running it from Android-Studio,
I tried running it from the terminal by entering the installed android folder then Sdk/tools and executing ./android as well as ./android sdk
I tried separately downloading stand-alone sdk tools and tried running it , but that didn't help too
I found such problems already dealt but in Windows, there the path is edited or the java_exe is set.
But i dint find any useful suggestion in case of Linux.
I am finding things really helpless by now. Please help!

Subclipse cannot load default SVN client, even though everything is installed properly

I'm having a problem with Subclipse, when trying to do anything like committing, updating or viewing history the first time nothing happens, and the second time I try this error show up:
All this used to work just fine but suddenly it stopped working. All the required packages are installed:
The "SVN interface" option in the preferences is empty/greyed out:
I have another Eclipse installation (Java EE) which has the same packages installed and everything is still working fine there.
I've already tried reinstalling all the SVN packages but to no avail. I'm running Eclipse Kepler on Linux Mint 16 Petra, SVN is version 1.7.9.
Any help would be greatly appreciated.
EDIT: I figured out that the other Eclipse installation had different (older) versions of the plugins. After updating these, that installation also stopped working. I suspect that my SVN version (1.7.9) is too old. I see 1.8.x has already been released, how can I install that version in my Linux installation? Running apt-get update/upgrade doesn't do it. I've seen some people talking about running dist-upgrade but that has broken things in the past so I'm very reluctant to do so unless absolutely necessary.
EDIT: I managed to install subversion 1.8.10 using these steps, but to no avail.
I managed to solve the issue my removing SVNKit and installing the "Subversion JavaHL Native Library Adapter" instead. I tried that before but it did work after I had also updated subversion to 1.8.

PyFITS installation error python version 3.3 is needed, which was not found in registry

When I try to install PyFITS I get the following error
python version 3.3 is needed, which was not found in registry
But I do have python 3.3 installed as well as numpy and Scipy. I would appreciate any help sorting this out. Thanks
OS---Windows 7 64bit
Python----3.3.2
This problem is actually addressed in the latest Astropy installation troubleshooting docs: http://docs.astropy.org/en/v0.2.4/install.html#the-windows-installer-can-t-find-python-in-the-registry
This issue is not unique to PyFITS, and has to do with whether or not the installation executable was built with UAC support, as well as whether your Python installation was installed "For all users" or "For the current user", as that affects which registry hierarchy Python installs its relevant keys into.
The script linked to in that documentation should fix up your registry with the correct entries so that the correct Python installation can be found regardless of how it was installed. But as with anything that messes with the registry please do handle with care.

Resources