Can't restart kernel due to content in stderr file #17252
Comments
|
BTW, I can start a new console without problems ("hamburger" menu of the console -> New console). |
|
Hey @mmagnuski, thanks for reporting. This is very strange indeed, but I don't think it's related to issue #17042. @dalthviz, could you check if this the case in a fresh conda-forge environment, using Python 3.9 on Windows? Thanks! |
|
Hi @ccordoba12, thanks for responding. Could it be that something is wrong with the environment that I use as the Python interpreter in Spyder? BTW, I've tested this with a fresh conda-forge Spyder env and I get the same problem. |
|
Hi @ccordoba12 @mmagnuski I checked creating a new env with conda-forge for the Spyder installation and setting a custom interpreter but the restart is working for me. @mmagnuski could you post here your custom interpreter env to check it? Also, could you run spyder in debug mode (from an Anaconda prompt run Maybe when doing the restart a traceback could be getting logged which could help us understand better what is happening in your case. Just in case, if you run the debug option from the interface, the file with the log should end up located at the spyder config directory under your user directory, something like Let us know! |
@dalthviz, what happens if you use the default interpreter instead? I mean, the same interpreter as the one in the environment you created? |
|
@ccordoba12 it restarts: |
|
Thanks for directions @dalthviz @ccordoba12!
This is the output of output of conda listThe output of |
|
Maybe not related with this but @ccordoba12 shouldn't the recipe for As the constraint on Checking @mmagnuski conda list output, and my own env, Regarding the log I guess it's related with the comms handling (I saw a similar log entry in #17042 ) but no idea :/ Just in case, pinging @impact27 for ideas |
|
@dalthviz I can check if downgrading |
|
I just wanted to highlight the fact that I get this error at startup ("System cannot find specified path") but after about 2 seconds it turns into normal text and the console can be interacted with: |
|
@mmagnuski regarding that error message, seems like could be related with invalid paths present in your PATH env variable. Could you check if all the paths in your PATH env variable are still valid? Also, just in case, please update to the new build for |
|
Thanks @dalthviz, I'm currently away from the machine that caused the problem, so I will let you know in about 2 days. |
|
This is similar to issue #17042 in the sense that if some text is present in the kernel stderr's file, then the kernel can't be restarted. We fixed that issue for the Windows installer, but this one shows that this is a general problem. @impact27, what do you think we should do about this? Perhaps trying to detect if a traceback is present in the stderr file and if not, ignore its contents when restarting? |
|
The problem is that |
|
|
|
Exactly, that's my idea too. But how can we infer that? |
ccordoba12
changed the title
ccordoba12
added
component:IPython Console
type:Bug
and removed
status:Awaiting Followup
labels
|
If "_when_prompt_is_ready" is called, the kernel did not crash during startup. |
|
🎉 |
Issue Report Checklist
conda update spyder(orpip, if not using Anaconda)jupyter qtconsole(if console-related)spyder --resetProblem Description
Hi, I have been trying for some time to set up Spyder in a separate conda environment to the env I'm working in (to avoid conflicts). Currently I have installed Spyder 5.2.2 from conda-forge in my base environment, and set the Python interpreter in Preferences to another environment called mne. I'm having an issue that seems to be similar to #17042 - I can't restart the kernel of the Spyder console (nothing happens if I try).
I also get "System nie może odnaleźć określonej ścieżki." (which means "System cannot find specified path") when the console starts, but I can write in the console after that.
Resetting preferences fixes the problem, but it also changes the Python interpreter to the one that I don't want to use (base env).
What steps reproduce the problem?
Versions
Dependencies
The text was updated successfully, but these errors were encountered: