ccordoba12
commented
1 year ago Hey @briswi, thanks for reporting. We'll check why Spyder-terminal is not working for Python 3.10 in the coming months. In the meantime, please use it with Python 3.9.
Open briswi opened 2 years ago
ccordoba12
commented
1 year ago Hey @briswi, thanks for reporting. We'll check why Spyder-terminal is not working for Python 3.10 in the coming months. In the meantime, please use it with Python 3.9.
dkinneyBU
commented
1 year ago Similar but different. Just installed Spyder 5.3.3. Notebook is fixed--yay! Terminal is broken--boo!
When I start spyder the Terminal pane is just blank. If I then create a new terminal, the pane populates for a few seconds, and then also goes blank. So, it's like it's trying to start and then fails or hangs.
ccordoba12
commented
1 year ago @dalthviz, could you check if Spyder-terminal is working for you using the env configuration mentioned by @dkinneyBU?
dalthviz
commented
1 year ago I was able to run the terminal normally (although indeed when starting Spyder you can see it as a blank pane, which I think is related with https://github.com/spyder-ide/spyder-terminal/issues/327). Just in case, this is the env conda list details where I tested (I have Windows 10 though):
A preview of what I'm seeing:
dkinneyBU
commented
1 year ago I completely uninstalled anaconda, and re-installed mini-conda, which packages Python 3.9.12, and I have the same results. @dalthviz you mentioned that it starts as a blank pane for you as well. What did you do to "wake it up"?
I also tried with both Powershell and Cmd--the results are the same.
dalthviz
commented
1 year ago @dkinneyBU I just wait for a bit and then the Terminal shows itself (I think the blank pane happens when the Terminal is still loading).
Could it be possible for you to start Spyder on debug mode and share the generated log? Maybe by cheking it we could determine the error happening when starting the Terminal in your case.
To generated the debug log output, run Spyder from an Anaconda prompt using the --debug-info verbose flag, so you will end up running something like spyder --debug-info verbose
dkinneyBU
commented
1 year ago Yeah, I can wait for an hour and it never starts up. :-( dkinneyBU_log.txt
I think I attached the log; if that didn't work let me know and I'll copy & paste.
thank you for the prompt assistance, I appreciate it!
dkinneyBU
commented
1 year ago My machine experiencing this issue is showing Python 3.10.6 in the Console. On a whim, I went through the same install process on my gaming laptop (both machines are running Windows 11). Terminal is working on that install, but this one is showing 3.9.12.
So, looks like this is likely a Python 3.10 thing, as the original issue logger stated. A little later today I will downgrade Python on my main machine to see if the issue goes away.
dkinneyBU
commented
1 year ago @dalthviz-- Welp... I create a new spyder environment with Python 3.9 and just installed spyder 5.3.3 and spyder-terminal--same results. But I did notice a whole boatload of these in the verbose debug log:
Uncaught ReferenceError: spyder_terminal is not defined Uncaught ReferenceError: spyder_terminal is not defined Uncaught ReferenceError: spyder_terminal is not defined Uncaught ReferenceError: spyder_terminal is not defined Uncaught ReferenceError: spyder_terminal is not defined Uncaught ReferenceError: spyder_terminal is not defined
ccordoba12
commented
1 year ago Don't worry, that's a harmless message.
dalthviz
commented
1 year ago After checking the debug log I'm seeing a couple of things that could be worthy to investigate:
urllib3 warning:
D:\Users\David\miniconda3\lib\site-packages\requests\__init__.py:102: RequestsDependencyWarning: urllib3 (1.26.8) or chardet (5.0.0)/charset_normalizer (2.0.4) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({})/charset_normalizer ({}) doesn't match a supported "2022-09-30 15:20:36,715 [DEBUG] [spyder.api.config.mixins] -> <spyder_terminal.widgets.terminalgui.TerminalWidget object at 0x000001F011084CA0> is observing __section in section appearance
WebSocket connection to 'ws://localhost:8889/api/kernels/5b44194b-67cf-475f-a658-ab79922f3836/channels?session_id=9d88076c-10f0-4a8b-ae70-e39598e91188' failed: Unknown reason
Connection lost, reconnecting in 1 seconds.Also, what happens if you try to access the url where the terminal server technically starts? I think it should be something like http://127.0.0.1:8071/
dkinneyBU
commented
1 year ago Hey sorry for the delay, it was a crazy week for me.
@dalthviz so that's interesting. If I hit that url the terminal works fine. So, just not working within Spyder??? Or maybe it's "working" but just not displaying correctly in the pane?
Also, in regards to the urllib3 message, I have the same version installed that you do, based on your conda list above.
dalthviz
commented
1 year ago Thanks for the feedback @dkinneyBU ! And then seems like for some reason the Terminal GUI is not able to stablish a connection with the started Terminal server which I guess is related with the Websocket - Connection lost, reconnecting in 1 seconds. message.
Also, just in case checked creating a new env with the conda-forge and Python 3.10.6 but is working for me 🤔
Env details:
However, I noticed something. If I launch Spyder from an Anaconda prompt I got the env name on the terminal, but if I run from the shortcut on the Start menu I got a terminal without that information:
From Anaconda prompt:
From Start menu shortcut:
Could it be that the envs where you are trying to use Spyder terminal you are mixing conda-channels? Could you compare the env details with your envs to see if there is any difference maybe related with packages like requests and urllib?
Description of your problem
This is similar to an already open issue (https://github.com/spyder-ide/spyder-terminal/issues/325). Submitting new issue as it is occurring for different versions and main components. What steps will reproduce the problem?
What is the expected output? What do you see instead? The spyder-terminal window appears within the spyder app, but there is no command prompt. After closing spyder, error message "The server that creates terminals failed to start." appears.
Please provide any additional information below As suggested by @steff456 in issue 325, I also created a new conda environment with python=3.9 and the error does not recur. However, the error message is occurring in any environment with python>=3.10, and the terminal window appears within spyder, but there is no prompt.
I start spyder from bash shell. Within environment with python=3.9.13, spyder starts and the spyder-terminal seems to be working properly. However, I see this (in the terminal that I started spyder from):
The first line of that readout,
fromIccProfile: failed minimal tag size sanity, also occurs when starting spyder in a conda environment without spyder-terminal installed (but still with python=3.9.13).In any environment with python>=3.10, there is no message on the terminal output regardless of whether spyder-terminal is installed or not.
Versions and main components
spyder_terminal_out.log spyder_terminal_err.log