-
-
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 6.0.An error occurred while starting the kernel (miniconda3) #23308
Comments
Hey @thomastskng, thanks for reporting. Please post a screenshot of what you're seeing in Spyder to better understand your problem. |
pasted the screenshot above. |
|
Thanks for the screenshot @thomastskng. I don't understand what could be happening in your case. @mrclary, could you check if you're able to reproduce this problem in your Windows VM? |
I cannot reproduce the error.
I have Windows 10 and conda 24.9.2. I also tried both Spyder build variants, @thomastskng, I would recommend starting Spyder in debug mode and pasting the log contents in a comment.
Ensure that the error is present, then quit Spyder and open the log file |
|
You had |
the environment is activated but spyder wouldn't launch with the |
The command is
not
(see the |
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
i am using miniconda (version: conda.24.11.1) in Window 10. I tried to install python 3.12 into a newly created virtual environment by running the following line with
conda create -n py312 -c conda-forge spyder-kernels scikit-learn nltk python=3.12 spyder
What steps reproduce the problem?
What is the expected output? What do you see instead?
I got this "an error occured whiule starting the kernel and & was unexpected at this time".
I tried switching the python interpreter from internal to C:\Users\me\minconda3\envs\py312\python.exe and vice versa, still get the same error.
Paste Traceback/Error Below (if applicable)
Versions
Dependencies
The text was updated successfully, but these errors were encountered: