Open arpitg95 opened 2 weeks ago
Hey @arpitg95, thanks for reporting. A couple of questions for you:
You said
Most of the time it just causes a black screen, and I have to restart the whole PC.
What do you by black screen? You don't even see the famous Windows blue screen of death?
What's your micromamba version?
libmamba version : 1.5.8 micromamba version : 1.5.8
What do you by black screen? You don't even see the famous Windows blue screen of death?
I tried launching spyder a few more times since then. One time I got the message that Windows had to sign me out because DWM.exe has crashed. So, it is not exactly a hard crash to BSoD.
Thanks for the extra info @arpitg95.
@dalthviz, could you check if you're getting the same behavior on Windows when using micromamba? For that you also need to apply the smalll fix mentioned by @arpitg95 in the OP.
So I checked installing Spyder 6.0.1 via micromamba and got a couple of messages from the installation:
Linking spyder-6.0.1-py312h2e8e312_2
error libmamba Creation of shortcut was not successful [json.exception.type_error.302] type must be string, but is object
"chcp" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
"chcp" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
""C:\Users\dalth\micromambaenv\condabin\micromamba"" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
Transaction finished
Launch Spyder via powershell showed another message:
C:\Users\dalth\micromambaenv\envs\micro_spyder\Lib\site-packages\qstylizer\style.py:68: SyntaxWarning: invalid escape sequence '\*'
_split_regex = '\*|\[[A-Za-z0-9=\'"_:]+\]|\W*\w*'
Checking the IPython Console I got an error but seems to me that is related with trying to activate the micromamba created env via the conda from the Anaconda distribution I have installed?:
"chcp" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<
Traceback (most recent call last):
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\exception_handler.py", line 17, in __call__
return func(*args, **kwargs)
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\cli\main.py", line 105, in main_sourced
print(activator.execute(), end="")
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 199, in execute
return getattr(self, self.command)()
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 165, in activate
builder_result = self.build_activate(self.env_name_or_prefix)
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 343, in build_activate
return self._build_activate_stack(env_name_or_prefix, False)
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 367, in _build_activate_stack
return self.build_reactivate()
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 558, in build_reactivate
self._replace_prefix_in_path(conda_prefix, conda_prefix)
File "C:\Users\dalth\anaconda3\lib\site‑packages\conda\activate.py", line 677, in _replace_prefix_in_path
if path_list[last_idx + 1] == library_bin_dir:
IndexError: list index out of range
`$ C:\Users\dalth\anaconda3\Scripts\conda‑script.py shell.cmd.exe activate C:\Users\dalth\micromambaenv\envs\micro_spyder`
Closed Spyder and did the micromamba.exe
change over kernelspec.py
, tried to launch Spyder but I got the same error
About that, I tried updating micromamba to 2.0.1 and I got the same chcp
error. It seems like micromamba 2.0.1 is not honoring the OS's PATH
, so it is not able to run system commands (You can check $Env:PATH
before and after activating micromamba environment).
I would recommend trying micromamba=1.5.10 (the last version before 2.x; I should also open an issue at micromamba repo).
Update: Seems like this is also an issue with mamba as raised in https://github.com/mamba-org/mamba/issues/3405 with a temporary fix.
@dalthviz, I agree with @arpitg95, please test with micromamba 1.5.10 because version 2.0 seems broken or semi-broken.
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
I am on Windows 11 and installed python, spyder, etc. using Micromamba. After updating from Spyder 5.5.6 to 6.0.x, I first encoutered the
--no-capture-output
error when Spyder tried to launch a kernel. That was kind of fixed on my end by modifyingenvs\<env_name>\Lib\site-packages\spyder\plugins\ipythonconsole\utils\kernelspec.py
-> micromamba to micromamba.exeThat being said, after launching spyder, it just plain crashes the PC. Sometimes it causes some other applications to close. One time it caused dwm.exe to crash. Most of the time it just causes a black screen, and I have to restart the whole PC. Though I did manage to see Spyder load the IPython kernel for a second before the screen crashed to black.
What steps reproduce the problem?
What is the expected output? What do you see instead?
Expected output - See spyder load ipython kernel Actual output - black screen
Paste Traceback/Error Below (if applicable)
Versions
Dependencies