After installing Spyder 5.1.5 into the Anaconda base environment using “conda install spyder=5.1.5”, when I try to run it I get the error “Image not detected!” and it actually comes up but the prompt window is hung. If I close the prompt window, Spyder closes as well and I am taken out of the base environment. It seems as if there is a conflict. Is there a way to go back to the earlier spyder version(4.1.4) in the anaconda base environment or do I need to delete spyder 5.1.5 and re-install spyder 4.1.4? Or would anyone know how to fix the conflict so I can keep spyder 5.1.5. I am on a Windows 10 PC with Anaconda 4.12.0(just recently updated).
you can downgrade spyder by using the command conda install spyder=4.1.4
I’m not sure why you are seeing the behavior you are seeing. Some things that would be helpful to know to try and figure it out:
If you launch Spyder from a terminal, are there any error messages there?
Can you share the output from conda info and conda list --show-channel-urls ?
Thanks for the help, Crystal. I did go back to version 4.2.5 just as you suggested and now spyder is working OK. Unfortunately, I am now having a problem with updating anaconda-navigator. Here is my (base) prompt message:
(base) C:\Users\Optimxr>conda update anaconda-navigator
Collecting package metadata (repodata.json): done
Solving environment: -
The environment is inconsistent, please check the package plan carefully
The following packages are causing the inconsistency:
- defaults/win-64::anaconda==5.3.1=py37_0
- defaults/win-64::astropy==3.0.4=py37hfa6e2cd_0
- defaults/win-64::bkcharts==0.2=py37_0
- defaults/win-64::blaze==0.11.3=py37_0
- defaults/win-64::bokeh==0.13.0=py37_0
- defaults/win-64::bottleneck==1.2.1=py37h452e1ab_1
- defaults/win-64::dask==0.19.1=py37_0
- defaults/win-64::datashape==0.5.4=py37_1
- defaults/win-64::h5py==2.8.0=py37h3bdd7fb_2
- defaults/win-64::imageio==2.4.1=py37_0
- defaults/win-64::matplotlib==2.2.3=py37hd159220_0
- defaults/win-64::mkl-service==1.1.2=py37hb217b18_5
- defaults/win-64::mkl_fft==1.0.4=py37h1e22a9b_1
- defaults/win-64::mkl_random==1.0.1=py37h77b88f5_1
- defaults/win-64::numba==0.39.0=py37h830ac7b_0
- defaults/win-64::numexpr==2.6.8=py37h9ef55f4_0
- defaults/win-64::numpy==1.15.1=py37ha559c80_0
- defaults/win-64::numpy-base==1.15.1=py37h8128ebf_0
- defaults/win-64::odo==0.5.1=py37_0
- defaults/win-64::pandas==0.23.4=py37h830ac7b_0
- defaults/win-64::patsy==0.5.0=py37_0
- defaults/win-64::pytables==3.4.4=py37he6f6034_0
- defaults/win-64::pytest-arraydiff==0.2=py37h39e3cac_0
- defaults/win-64::pytest-astropy==0.4.0=py37_0
- defaults/win-64::pytest-doctestplus==0.1.3=py37_0
- defaults/win-64::pywavelets==1.0.0=py37h452e1ab_0
- defaults/win-64::scikit-image==0.14.0=py37h6538335_1
- defaults/win-64::scikit-learn==0.19.2=py37heebcf9a_0
- defaults/win-64::scipy==1.1.0=py37h4f6bf74_1
- defaults/win-64::seaborn==0.9.0=py37_0
- defaults/win-64::statsmodels==0.9.0=py37h452e1ab_0
What would you suggest I do. I have done “conda update anaconda --all” successfully just before this problem.
I’d recommend doing a conda install anaconda=custom
I think you are running into trouble because your anaconda metapackage is pinned to v5.3.1.
Thanks for the advice. Do I need to uninstall the current anaconda3 first? What specifically does “=custom” do for the installation? Does it install fewer packages than the normal install?
You do not need to uninstall the current anaconda3. There is a metapackage called “anaconda” that pins the versions of certain packages within it. This metapackage has a special version “custom” which unpins all the packages within it - which once set, allows you to install packages of different versions of your choice, instead of the particular ones pinned with the Anaconda Installer releases.
Hi Crystal, I did the anaconda=custom install successfully and it downloaded the following:
anaconda 5.3.1py37_0–>custom-py37_1
mkl 2019.0-188–>2018.0.3-1
When I run Navigator from the anaconda prompt, anaconda3>anaconda-navigator, I see the following display and the green circle with …loading applications… it just hangs at this point.
Am I missing something here. This doesn’t seem to solve my problem with Navigator. Are there packages that need to be downloaded before Navigator will run OK?
Were you able to update Navigator, after you updated the anaconda metapackage to custom? What version of Navigator do you have now? The traceback in your anaconda prompt does provide some clue as to what may be going wrong - but I don’t happen to know the solution offhand.
Hi @CrystalS
I could not launch spyder on the root environment and have trouble using 4.1.4 edition. I have been
current version: 4.12.0 of conda.
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:
- spyder=4.1.4 → python[version=’>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0’]
Your python: python=3.9
If python is on the left-most side of the chain, that’s the version you’ve asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.
What is the error you are seeing with your installation of Spyder?
Can you try launching it from a terminal to see if you see an error or if it works from there?
I don’t believe Python 3.9 was released yet, when Spyder v4.1.4 was built - so there won’t be a version of it for Python 3.9. Looks like the oldest version of Spyder available for Python 3.9 is v4.2.0. However, I would expect a more recent version should work for you. The latest release of Spyder available at the moment is v5.1.5.