Spyder Version 3 Download
Sebrina Lobianco
A big thank you to all the contributors that made this release possible: @kevinsmia1939 @juliangilbey @mrclary @ccordoba12 @musicinmybrain @dalthviz @conradolandia @bnavigator @remisalmon @spyder-bot (our translators) ?
However, a "pip" install works to get spyder going with the latest version since it really doesn't care about the arcpy/arcgis issues, you may not have a bug free experience with Pro or its notebook functionality, but that depends on what you do with Pro
So I've similarly been messing with this this week. I got a fresh install of ArcPro 3.0.1 on my machine and cloned the default env through package manager, activated my clone, restarted Arc, then downloaded spyder 5.1.5 through package manager to my clone env successfully. I open spyder through my clone env / scripts and then spyder opens and I made sure it is also set to my clone env here.
I go to the console and 'import arcpy' but get the attached messages despite seeing that Arcpy is in my clone env and that spyder is set to my clone env. Feeling at a loss with this. Would love to hear input on why arcpy will not work with spyder.
All I did was install SPyder 5.1.5 to my clone with the ArcPro package manager. Then I followed the suggestions in the attached post to create a desktop shortcut as Dan suggests below. It imports arcpy and I can use all those tools fine. There are just issues with some other random things. Here's a link to the instructions I followed: -pro-blog/installing-spyder-ide-for-arcpro/ba-p/901923
Try a shortcut on your desktop. You need to execute the spyder-script.py script using python in your clone. YHou still can't update beyond 5.1.5 because of things pinned and a convoluted dependency path which is being impeded somewhere along the trail.
I updated to Arcgis Pro 2.9 and now I am unable to use spyder. I was able (once!) to get a version (5.x) of spyder up and running, but unfortunately, to do so broke my numpy version and the rollback to a previous version was unsuccessful.
Now, when I clone the default environment, spyder 3.7 is installed (not 5.x) and is not able to connect to the correct interpretter. I have tried setting it manually using the preferences in spyder, but this doesn't work.
You won't be able to update spyder to 5.3.x either since it hasn't been updated in the anaconda site for at least 4 months. If you need the most recent version of spyder, use one of their installer in a separate environment devoid of arcpy and arcgis.
Thanks for the information. Unfortunately, that did not work. It resulted in a lot of version inconsistencies/incompatibilities (too many to list here). I have tried to find out if there is a mismatch between spyder 5.1.5 and python 3.7.11, but can't find any information. I am trying to install spyder in a clone of arcgispro-py3. The behavior of conda when trying to install spyder is different depending on if I attempt to install in arcgispro-py3 or a arcgispro-py3-clone. When installing in arcgispro-py3, conda attempts to downgrade arcgispro to 2.7 (which is what I am trying to avoid), while this doesn't happen with the clone.
Thanks for posting plan C. I created a clone environment and when attempting to install the Spyder package it would fail every time. I open the Python Command Prompt and typed in pip install spyder and it appears to be downloading with all the dependencies. Currently using ArcGIS Pro 3.1.0.
But get the error "ERROR: Could not install packages due to an OSError: [WinError 5] Access is denied: 'C:\Users\##\Anaconda3\envs\spyder\Lib\site-packages\PyQt5\QtCore.pyd'Consider using the --user option or check the permissions."
Spyder should be installed when you install the anacondadistribution. However, if spyder has not been installed (observedonce on a Mac M2 in December 2022), then use the command condainstall spyder to install it.
The AUR package is over one year old. Also, it conflits with the official Community package.
Make a complete uninstall of both (including dependencies) and then try installing 5.4.1 with:
sudo pacman -Syu spyder
In this case, as the first few hits on both point to, the issue is spyder-ide/spyder#17616 and has already been fixed in Spyder 5.3.0, which we released some time ago. However, Anaconda still has not updated their version to it (their latest being 5.1.5), which we have no control over.
For an up to date, fully supported and tested version of Spyder, you can either install it from Conda-Forge in a fresh Anaconda environment, or from our standalone Windows installer, as Carlos describes in his comment there. It will still work with all your existing environments, provided you update the version of spyder-kernels in them to 2.3.0 or later (which you may need to install from the conda-forge channel as well, if Anaconda is still not up to date).
Since professors have recommended us to use spider 5 (you can see it here), and they always tell to use spyder just to be ready for it on the exam day, I assume there will be no major differences between the latest spyder version and the one downloaded on laboratories' PCs. Moreover, I use spyder 5.3.3 on my PC and I have not any problem in using 3.2.8, so I think that using the latest version on yours will be fine as well.
Spyder is a free and open-source IDE developed by and for scientists whouse Python. It is included by default in the base environment when youinstall Anaconda, and can be started from a terminal with the commandspyder (or on Windows or macOS, launched from the Anaconda Navigator GUI).It can also be installed with dedicated installers.To avoid dependency conflicts with Spyder, you should install mne in aseparate environment, as explained in previous sections. Then, instructSpyder to use the mne environment as its default interpreter by openingSpyder and navigating toTools > Preferences > Python Interpreter > Use the following interpreter.There, paste the output of the following terminal commands:
If the Spyder console can not start because spyder-kernels is missing,install the required version in the mne environment with the followingcommands in the terminal, where you replace ... with the exact version ofspyder-kernels that Spyder tells you it requires.
After this, I launched spyder from (base) and changed console settings to use /home/mpettet/anaconda3/envs/mne23/bin/python, as instructed, then quit and relaunched spyder. I still get the same spyder-kernels version error as my previous posting.
The following command:
(mne23) mpettet@aloha:$ conda install spyder-kernels=1.9.4
definitely seems to do what we want, but sadly, fails after about 15 minutes, disgorging an epic stream of output detailing all the unresolvable conflicts.