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.
Related
I am using a MacBook Pro (early-2011) with macOS Sierra v10.12.6. I can not install and run Anaconda3. I have downloaded the pkg file from the Anaconda webpage. First day, it took overnight to finish installing. After which it said installation failed. I tried to delete all files and reinstall all over again serval times, but this hasn't worked. I made sure the /opt folder was empty before I reinstall again, but even like that didn't work.
Any ideas how to make it work?
Had a similiar problem with a geriatric iMac mid 2010 running OSX 10.13.16. The GUI installer for Anaconda 3 takes an age, then reports there was a problem.
I downloaded the install script and ran, "bash Anaconda3-2022.05-MacOSX-x86_64.sh" in a terminal.
Answered questions, and after some time, have Anaconda installed in my personal space. Now to figure out how to use the latest LTS Julia.
No Anaconda support. Current Anaconda (and likely Miniconda) distribution declares a minimum system requirement of macOS v10.13+. One could try scraping back through the archive to find an older distribution that will install, but I wouldn't recommend that.
Conda Forge supports macOS 10.9+. Conda Forge still builds all osx-64 packages with a macOS 10.9 target. Hence, you should be fine using instead a Miniforge variant for the base Conda installation. I strongly recommend Mambaforge, and using mamba instead of conda.
Mac OS 12.2.1
Anaconda Navigator 2.1.2
Spyder 5.1.5
I’ve been to the Spyder Web site, performed what was described as “Basic First-Aid” as well as “Emergency CPR” without satisfactory resolution. The first symptom was that the debugger just hung. After performing the suggested fixes (updating Anaconda, Spyder, and Spyder dependencies, system re-boot, etc.), the debugger now reports: “OperationalError: attempt to write a readonly database.”
I’m at my wits’ end. I’m wondering if I need to completely re-install all of Anaconda. Is there a “best way” to do this? Is there a web site that I can consult that will demonstrate how to get a fresh installation?
ADDENDUM
So, I cleaned Anaconda from my machine (what a horrific experience!) and re-installed it, using conda for both tasks. I started Anaconda and then launched Spyder. Then I loaded one of my modules, set a brake-point in the editor, and boom! The Spyder debugger worked. However, the new installation of Anaconda was lacking a particular library: pyreadstat. I used conda to get this library. I then launched Anaconda again, saw that pyreadstat was now in the base(root) environment. I ran one of my packages (8 modules mainly consisting of numpy and itertools manipulations of N-D arrays) and everything worked, including calls to pyreadstat to read SAS datasets. Okay, everything seemed copacetic. So, I tried to debug one of my modules and the debugger failed again, returning the message: “OperationalError: attempt to write a readonly database.” WTF! Is conda trashing Spyder’s debugger in some mysterious way? I don’t get it. Why would pyreadstat affect Spyder. It must be conda.
To answer my own question, in the Mac Terminal app, I typed:
--> conda install -c conda-forge spyder=5.2.2
Boom! All is well.
I had the same problem on Windows10 with spyder version 5.1.5.
For me, updating Spyder to the newest version as suggested here worked as well. This can be done in two ways:
Console
Open the console or, if you're working on Windows, the Anaconda Prompt and type the following commands in order to first uninstall spyder, and then re-install the newest version (just updating didn't work for me).
conda remove -n myenv spyder
conda install -n myenv -c conda-forge spyder
The first command, remove, uninstalls spyder in the virtualenv called 'myenv'. If you don't use virtualenvs, just leave the -n myenv aside.
The second command, install installs spyder from the third-party channel conda-forge instead of the official channel defaults. This option is necessary in order to install a spyder version newer than 5.1.5
Anaconda Navigator
Uninstall Spyder: In the "Home" tab, select the correct virtual environment in the "Applications on" dropdown menu. Then click on the gear symbol in the upper right corner of the spyder tile and select "remove application".
Add conda-forge to your environment's channels: This is nicely described at the bottom of this page.
Install spyder again, in the way you did it the first time.
Click again on the gear on the spyder tile, choose "install specific version" in order to update to the newest version. Now, versions newer than 5.1.5 should be available.
I have installed the Anaconda 3 in my windows 10 and it has not installed the Scripts folder and the Anaconda Prompt or Navigator applications.
I have come here and in other sources for an answer and tried to reinstall, use the cmd as adm to install with the conda commands, but the system does not recognize the conda command. I have seen answers with the Scripts folder, but it was not installed.
I have also seen answers advising me to install miniconda and then update to anaconda, but again, miniconda has the same problem as anaconda: no scripts folder, no recognition of the conda command.
I don't know what to do.
Dear all who may have had the same problem, what worked for me was to install the 32-bit version, I had heard it was more stable.
I did not have to restart Windows after installing this version, It was already there, Anaconda Prompt and Navigator.
I work on a hp Probook with windows 10 and the problem was that the application hp Sure Sense Installer block the installation of anaconda. After uninstalling the hp Sure Sense Installer application and reinstalling anaconda, everything works fine !
I installed Trac on Windows 7 using Trac-1.0.1.win32.exe.
How do I cleanly uninstall this? My reason for uninstalling is that I installed it with Python 3.4, and then discovered that it actually requires Python 2.7. So I would like to remove the existing install, and re-install it for Python 2.7 .
Nothing appears for Trac in the Windows 7 "Add/Remove Programs" area. There is a program RemoveTrac.exe that was created under the Python34 directory, however when I run that it pops up a MessageBox with title Runtime Error and text This program is normally started by windows, and it does not uninstall.
I'm not sure but to me it seems that installer just checks your environment, detects some pathes and sets them in the installed Trac environment. Trac should be on top of Python and SVN. So likely, you can just remove the installed Trac directory.
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.