- #How to change preferences in python install#
- #How to change preferences in python update#
- #How to change preferences in python windows#
Sys.version_info(major=3, minor=8, micro=3, releaselevel='final', serial=0) Type "help", "copyright", "credits" or "license" for more information.
Users/drmccloy/opt/anaconda3/envs/test/bin/python What else can I do to help troubleshoot this? Again, here is evidence that there is nothing "invalid" about the path I'm trying to set: (base) ~ % conda activate test This problem could be fixed by restarting Spyder. I also get another dialog after a few seconds:Ĭompletion and linting in the editor for Python files will not work during the current session, or stopped working. Invalid file path: /Users/drmccloy/opt/anaconda3/envs/test/bin/python3.8 Now, when I launch Spyder from the base environment (the only env where it's installed) and try to set the python executable, I get this error: Here is confirmation that I'm using the correct versions: (base) ~ % conda list | grep spyder So I tested them and, if anything, the results are now slightly worse than before. I noticed that spyder 4.1.4 and spyder-kernels 1.9.2 dropped on the defaults channel today. > assert spyder_version = console_version > pyexec = '/Users/drmccloy/opt/anaconda3/envs/test/bin/python' '/Users/drmccloy/opt/anaconda3/bin/python' I'm also somewhat puzzled because the following snippet works in a macOS python REPL: > import sys
#How to change preferences in python windows#
Note that this problem does not occur under Windows or Linux I have successfully set up the "modular approach" on both of those OSes in the last couple of weeks in both cases Spyder was installed in an environment running Python 3.7, and I was able to set the console to use Python 3.8 from a different environment. Not applicable internal console shows only startup greeting and empty prompt Versions Paste Traceback/Error Below (if applicable) Note that if step 2 above is changed to conda create -n test python=3.7 spyder-kernels then it is possible to set the interpreter, so it appears to be something specific about Python 3.8 that is the problem. The message is accurate the console interpreter has in fact stayed as the spyder-internal console (confirmed by import sys print(sys.executable). You selected an invalid Python interpreter for the console so the previous interpreter will stay. What is the expected output? What do you see instead?Įxpected: consoles will use the Python 3.8 interpreter. Try to set the Python interpreter Preferences > Python Interpreter > Use the following Python interpreter to /Users/username/opt/anaconda3/envs/test/bin/python.Launch spyder from the base environment (either from terminal or through Anaconda Navigator GUI).conda create -n test python=3.8 spyder-kernels.There appears to be nothing "invalid" about it. I have checked, and the Python interpreter I'm trying to use is marked as executable, and can be used in a terminal shell to launch a Python REPL session.
#How to change preferences in python install#
On a fresh copy of macOS 10.15.5 ("Catalina"), with a fresh install of Anaconda, it does not appear to be possible to use what your docs call "the modular approach" to set the Python interpreter if Spyder is runing under Python 3.7 and the desired version of the interpreter is Python 3.8.
#How to change preferences in python update#
Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda).