MRG: bump spyder version

[drammock]

closes #8009

currently WIP because the fix doesn't actually work in my local testing; waiting to hear back from Spyder devs.

[drammock]

@ccordoba12 says he can successfully set a py3.8 interpreter within an instance of spyder running in a py3.7 environment, on a bare-metal mac (although I've not been able to replicate this when running OSX catalina in a VM); see spyder-ide/spyder#13252 for discussion. Do any of our devs have a mac running catalina where they could double-check / confirm that this works? The procedure is:

conda create -n test-spyder python=3.7 spyder
conda create -n test-py38 python=3.8 spyder-kernels
conda activate test-spyder
spyder &

...and then go into spyder preferences and try to set Tools > Preferences > Python Interpreter > Use the following interpreter to the value of conda activate test-py38 && python -c "import sys; print(sys.executable)". Then close the running ipython console (should be py3.7) and see if the automatically spawned replacement console is py3.8.

Once we get confirmation, this PR is ready for review/merge. All CIs are happy except codecov (why, codecov? this PR only touches docs and the environment file)

[larsoner]

@drammock I'm on Catalina and ran those commands (after conda update -n base conda just to be safe) and when I do Python->Preferences, then Python Interpreter, then paste in the value of conda activate test-py38 && python -c "import sys; print(sys.executable)" I get the error:

Invalid file path:
conda activate test-py38 && python -c "import sys; print(sys.executable)"

[larsoner]

FWIW it looks like it's Spyder 4.1.5 according to the "About Spyder"

[drammock]

@larsoner my instructions were not clear. in a terminal, run conda activate test-py38 && python -c "import sys; print(sys.executable)" and paste the path that it returns into the "use the following interpreter" box.

[larsoner]

For me that's /Users/larsoner/opt/miniconda3/envs/test-py38/bin/python and it appears not to work:

[drammock]

@larsoner can you confirm that you do indeed have spyder-kernels installed in that env and it's a high enough version?
conda activate test-py38 && conda list spyder-kernels

[larsoner]

$ conda activate test-py38 && conda list spyder-kernels
# packages in environment at /Users/larsoner/opt/miniconda3/envs/test-py38:
#
# Name                    Version                   Build  Channel
spyder-kernels            1.9.4                    py38_0  

[larsoner]

@drammock thoughts on this for 0.22, or just bump to 0.23?

[drammock]

spyder devs have failed to replicate. Personally I don't have the patience to debug this any further; working inside the OSX VM is really slow for me (I have all the wrong muscle memories, and some keyboard shortcuts get stolen by the host OS). Unless an actual mac user is willing to take over here and in spyder-ide/spyder#13252, I think we have 2 choices:

1. close this and pretend nothing is wrong.
2. assume that yours and my experiences are some kind of fluke or user error, and go ahead and rebase+merge this PR.

[larsoner]

I dug into it and replied to the upstream issue -- they require spyder_kernels < 1.10 but 1.10 is the only version available for 3.8. Let's see what they say

[drammock]

this one should (finally) be good to go

[larsoner]

Thanks @drammock @ccordoba12 !