-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spyder kernel unable to start after switching default environment to Anaconda #20942
Comments
Hey @TradeMark17, thanks for reporting. We'll take a look at it to see what's happening. @dalthviz, could you check if you can reproduce this problem? According to what @TradeMark17 posted above, you need to create an env with Python 3.10.9 and Pytorch, and try to connect it to our Windows installer. |
I was unable to get the same message but creating an env with something like Or the console gets stuck showing the loading page Env details:
Checked installing Spyder for the current user in the default installation and seems like you can see either a message about the kernel continuously restarting or the loading page too Further checking by creating a conda env with something like @TradeMark17 could you share here the link with the steps you followed to install pytorch/torch? Did you followed those steps in you base environment? and also, is possible for you to create an env using a more recent version of Python 3.10 (like Python 3.10.11)? Let us know! |
Thank you both for your responses! @dalthviz I also got the spyder continuous restarting error. When I connect to the default console the console works but I am unable to use the Torch package. I installed PyTorch (Torch) according to the steps in their installer with this command:
I think I did it in the base environment? I'm not really sure what environments do. The only time I run terminal commands is when people on GitHub or StackExchange say it will help hahah... I tried copying your conda env code above and I have the same issue. |
Thanks for the extra info @TradeMark17! @dalthviz, so it seems the problem is that we're failing to show the kernel error message about Spyder-kernels not being installed in the selected env, right? |
Not sure, in my case the env where the console doesn't start properly has However, seems like @TradeMark17 installed Not totally sure what could be happening here, sorry |
Ok, that's good to know. @TradeMark17, could you check that on your side and let us know if the error is solved for you? |
@ccordoba12 I will try this! How do I make a new env with conda-forge packages? |
You need to use However, it seems that channel doesn't have the |
Closing this as a duplicate of issue #21338, which will be fixed in our next version (5.5.0), to be released at the end of the month. |
Description
What steps will reproduce the problem?
Sorry in advance, I do not know much about environments or windows applications.
I have Anaconda and Spyder (5.4.3) both downloaded on my Windows desktop, and I am running Spyder from the .exe file (because it's broken through Anaconda Navigator). Python version 3.10.9.
I need to use the module/package "torch", which is not already downloaded with Spyder. I followed the instructions on the PyTorch website, and the package got downloaded to an Anaconda folder. Spyder doesn't see "torch" when run with the default environment, but when I switch the default environment to that which is printed out by this command in the Anaconda Powershell Prompt:
python -c "import sys; print(sys.executable)"
the kernel won't start - error message: "& was unexpected at this time". I've uninstalled and reinstalled Spyder and Anaconda 3 times so far and each time I get more errors, I am going crazy.
Traceback
Versions
Dependencies
The text was updated successfully, but these errors were encountered: