After updating to Pro 2.3 and cloning the default env to two different envs I get this error when I start Spyder:
Not sure what's up with that; anybody else getting it?
Solved! Go to Solution.
Joe....
seem like you are trying to run spyder.exe directly...
create a shortcut as suggested in my many blogs
Target
C:\arc_pro\bin\Python\envs\arcgispro-py3\pythonw.exe "C:\arc_pro\bin\Python\envs\arcgispro-py3\Scripts\spyder-script.py"
start in
C:\arc_pro\bin\Python\envs\arcgispro-py3\Scripts
This happens to be for where it is installed in the default ArcGISpro-py3 environment...
Just change the bold-faced text above with your paths.
Joe....
seem like you are trying to run spyder.exe directly...
create a shortcut as suggested in my many blogs
Target
C:\arc_pro\bin\Python\envs\arcgispro-py3\pythonw.exe "C:\arc_pro\bin\Python\envs\arcgispro-py3\Scripts\spyder-script.py"
start in
C:\arc_pro\bin\Python\envs\arcgispro-py3\Scripts
This happens to be for where it is installed in the default ArcGISpro-py3 environment...
Just change the bold-faced text above with your paths.
Guilty as charged.... But, now I'm getting the original error with a different presentation:
Checking git hub now.....
eta:
In a Python command window type
conda update spyder
I think the problem stemmed from installing the spyder-kernal package that is bundled with Pro 2.3: conda tossed:
Thanks Dan!
I am using 3.3.2 with spyder-kernels 0.3.0 There was a huge leap in spyder-kernels to 1.0.? when I ran
conda update spyder-kernels --dry-run
I suspect it has to do with spyder 4 being released some time this quarter.
I normally update the main package (spyder) and leave other stuff alone unless I check it out on GitHub first to see if there are peripheral issues.
My Spyder is now 3.3.2...