nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 2.8 & spyder

ChadFerguson1

I just installed ArcGIS Pro 2.8 and it appears that if I want to install spyder it is going to install v. 3.3.6. This is archaic. When I attempt this in conda it tells me if I do install, that it will downgrade both arcgispro and arcpy to 2.7

How can I get a more modern version of spyder for ArcGIS Pro 2.8??

Encontre mais publicações marcadas com

Accepted answers

JoeBorgione

Are you at 2.8.0? If so, that release had a bunch of problems with adding packages and clones. Upgrade tp 2.8.2. I used the conda install command on my 2.8.2 install. I had installed 2.8 but backed it out when I ran into the problems.

All comments

HanZheng

Yes. I also noticed that 5.15 became available in conda lately. Previously it could bring me as far as 5.0.5 and 5.15 was not in the library.

OSU_R_Webb

More recently, on 2.9.3, I experienced this issue. I found that after cloning the environment, you must install spyder (which initially only shows v 3.*), then uninstall the spyder package. When you go back in to Add Packages, Spyder 5.1.5 will *magically* be available to install. This fixes issues with Spyder 3.* failing to initialize (which from sleuthing seems to be because of associated dependencies being too new for v.3's requirements).

While this is not ideal, I found it to work for my use case.

HanZheng

Neverminded.

I probably messed up something else during the process. I deleted the cloned environment and cloned a new one in ArcGIS Pro 2.9.2. Although I never found out why it got wrong in the first place, at least the Spyder 5.1.5 is working now with ArcGIS Pro 2.9.2

One thing I noticed (it probably was not the case for others) is that while I was using either Spyder 5.0.5 or 5.1.5, this error always came out in Python Command Prompt.

link image0 hasn't been detected spyder

Although this doesn't really stop Spyder from launching in my machine, the process in python command prompt seems to be stalled. So if I accidentally closed the Python cmd, it will shut down the Spyder as well, which is quite annoying.

I know this is not a good suggestion, but what I did was to use pip to install an even newer Spyder (5.2.2) that is not in Conda's library.

Another thing I learned this time is that do never do "conda update spyder" because it will bring you back to problematic Spyder 3.3.6.

HanZheng

Spyder 5.0.5 still works while I was using ArcGIS Pro 2.9.1.

Yesterday I upgraded to 2.9.2 and it started showing up these when I tried to start Spyder in Python Command Prompt although I am 100% sure if it is related to the new update.

PhilipWhite1

Thanks Alex,

Nope, couldn't get it successfully installed.. after seeing your message, i tried:

conda install -c esri spyder -y

Following these instructions: https://env859.github.io/python/spyder.html. So thanks Duke University!

By installing from esri channel it seemed to work without going through the downgrading and upgrading arcpy steps. Well, until it doesn't . 🙂

If this blows up I'll try that.

Thanks! Didn't follow your method but it let me in the right direction anyway.

Phil

AlexanderStum

First question, did you already install spyder? If not, install spyder, don't worry about version at this step, just get a version, let conda pick what's acceptable.

Second, now try updating everything with conda upate -all? This will demote your ESRI modules, but that is okay. After you have updated everything, namely Spyder, you will fix that.

Third, now do conda install arcpy=2.9. This will revert the demotion of your ESRI modules but will leave most else updated.

PhilipWhite1

This software just never fails to disappoint.

Same problem: Fresh install of 2.9. Cloned environment, install spyder, wait, blow up.

(arcgispro-spy) C:\arc_pro\bin\Python\envs\arcgispro-spy>conda install spyder=5.1.5 --no-pin
Collecting package metadata (current_repodata.json): done
Solving environment: |
The environment is inconsistent, please check the package plan carefully
The following packages are causing the inconsistency:

  - esri/win-64::arcgis==1.9.1=py37_2327
  - esri/win-64::arcpy==2.9=py37_arcgispro_32704
  - esri/win-64::cftime==1.5.0=py37_1
  - esri/win-64::gdal==3.3.0=arcgispro_py37_16778
  - esri/win-64::h5py==2.10.0=py37_arcgispro_12
  - esri/noarch::lerc==2.2=py_0
  - esri/win-64::matplotlib==3.4.2=py37_arcgispro_1
  - defaults/win-64::mkl-service==2.3.0=py37h196d8e1_0
  - defaults/win-64::mkl_fft==1.3.0=py37h46781fe_0
  - esri/win-64::mkl_random==1.2.0=py37_0
  - esri/win-64::netcdf4==1.5.7=py37_arcgispro_2
  - defaults/win-64::numexpr==2.7.3=py37hcbcaa1e_0
  - esri/win-64::numpy==1.20.1=py37_0
  - defaults/win-64::pandas==1.2.3=py37hf11a4ad_0
  - esri/noarch::saspy==3.7.3=py_0
  - defaults/win-64::scipy==1.6.2=py37h14eb087_0
  - esri/win-64::swat==1.9.3=py37_0
  - defaults/noarch::xarray==0.17.0=pyhd3eb1b0_0

After that just a littany of conflicts.

I actually thought I had this working on 2.8 somehow... arcpy would import fine then the kernel would crash anytime you tried to use it. I had hoped upgrading to 2.9 might remedy... ha!

danretired

and I have Pro 2.9 and Spyder 5.15 installed in the main environment (no clone)

maybe in retirement things just go more smoothly 😉

JoeBorgione

The above solution above doesn't seem to work for Pro versions 2.8 ...

Well, I have Pro 2.8.2 installed and Spyder 5.0.5 installed in a cloned environment and things are working smoothly. I'm two weeks out from retirement and plan to enjoy the time I have left, so I won't be upgrading to 2.9.0 anytime soon....

AlexanderStum

The above solution above doesn't seem to work for Pro versions 2.8 and 2.9.

Anytime the approaches above are tried, --no-pin etc., it starts with this message:

"The environment is inconsistent, please check the package plan carefully
The following packages are causing the inconsistency:"

And ultimately fails to update spyder or spyder-kernels. I found a two-step work around that worked, though I recommend it only be applied to a cloned environment. First update all packages, and let conda discern what's the optimal set up.

conda upate -all

Yes this will ask you to downgrade arcpy to v. 2.7 as well as other attendant ESRI packages. This will make it incompatible with the installed version. The second step will amend this. Frankly this is a testament that ESRI has failed to put together a stable Python package for versions 2.8 and 2.9.... Now update arcpy by installing the correct version.

conda install arcpy=2.8 #or 2.9 per installed version

This will update arcpy and attendant ESRI packages, but will leave most other updates, including spyder, alone.

ChadFerguson1

Our organization only has version 2.8.0 certified for installation. As JoeB suggested there are known problems with that version I gave up and rolled back to 2.7.3.

So at least I am back up and running.

I squandered about a day and a half for nothing. Simply unbelievable.

Thanks for the suggestions and tips!

danretired

conda install spyder=5.0.5 --no-pin

should work, or specify the "default" channel, in just change your .condarc file

you can switch the order of precedence if you like to live on the edge

C:\your_install_folder\bin\Python

open in a text editor, it will look like this

channels:
- esri
- defaults

change to...

channels:
- defaults
- esri

I have been using spyder for years and yes, they need to remove the old version of spyder from their channel or keep pace with the times.

JoeBorgione

ChadFerguson1

I tried that but got a laundry list of reasons why it's incompatible

Of all the messages I received, this might help narrow it down??

Your python: esri/win-64::python==3.7.10=0

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.

JoeBorgione

Open a python command prompt window in your cloned environment and do it with a conda command:

conda install spyder=5.0.4

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.