Spyder not opening after conda update #12557
Comments
|
Hi @srvmig Its seems the module Please run
and try again Cheers! |
|
Worked !! Thanks..... |
|
Glad it worked out! |
|
Not sure this issue should be close @goanpeca . I just had the same error OS: Windows 10 conda list |
|
Hello, it is a problem with the latest pylint package released by Anaconda so while a new package is fixed and released, this issue will persist and the “solution” is to install toml manually in the meantime. |
|
I updated the recipe and pinged the Anaconda devs, so we hopefully have a fix soon: |
|
@goanpeca Just to note, this was particularly worrysome for users on Windows since when launching Spyder from the shortcut (our recommended method on that platform), Spyder appears to launch, the splash screen shows, but then at the point near when it usually vanishes to show the mainwindow UI, it silently exits instead leaving the user with no indication of what happened that would lead them here to the fix; I didn't get a "Spyder failed to start" dialog despite many restarts. As a Spyder core dev who has troubleshooted and helped resolve hundreds, perhaps thousands of different issues like this, it only took a couple minutes to diagnose and solve but I worry the average user without that fortunate experience might find it far more frustrating. Maybe there's something we can do to improve this UX? |
|
Maybe we could add an additional icon to open Spyder in debug mode on windows? What do you think @ccordoba12 |
|
That wouldn't work in this case because Spyder doesn't even start due to this issue. The only solution that occurs to me is to use self-contained, well-tested installers that won't be affected by this kind of bugs. @CAM-Gerlach, do you have something else in mind? |
Yeah; the fundamental issue is that no feedback at all is presented to the user when Spyder fails to start early enough in initialization, at least before the mainwindow GUI is displayed, unless its run from a terminal.
Not sure; the installers as discussed will hopefully mitigate most startup issues once and for all, but even with full control over the Python level of the environment and ignoring random corruption and deliberate user action, there is always a chance of an error occurring at some point during initialization due to something in the user's/OS/machine environment outside of our direct control. In the case of a startup failure, IMO the UX priority is to at least convey to the user that A. An error occurred, and B. Enough information (error message, traceback, etc) to Google or report it. Right now on Windows with the shortcut, there is no feedback, Spyder simply never launches. I had no idea it was even an error until I ran it from the command line, since Spyder went through the normal splash screen process but then the GUI never displayed, so I didn't have a way to know what had actually happened or (without running it in the command line, which the average user may not know to do) what to do about it. I'll open a new issue discussing this further and some postulated solutions, as we discussed in our call. Thanks! |
Issue Report Checklist
conda update spyder(orpip, if not using Anaconda)jupyter qtconsole(if console-related)spyder --resetProblem Description
After updating through
condo update --allmy spyder is not opening/starting at all.What steps reproduce the problem?
What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)
Traceback (most recent call last): File "C:\Users\ASUS\Anaconda3\Scripts\spyder-script.py", line 10, in sys.exit(main()) File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\app\start.py", line 205, in main mainwindow.main() File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\app\mainwindow.py", line 3734, in main mainwindow = run_spyder(app, options, args) File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\app\mainwindow.py", line 3590, in run_spyder main.setup() File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\app\mainwindow.py", line 977, in setup 'spyder.plugins.{}'.format(plugin_name)) File "C:\Users\ASUS\Anaconda3\lib\importlib\__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1006, in _gcd_import File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\plugins\pylint\__init__.py", line 14, in from .plugin import Pylint as PLUGIN_CLASS File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\plugins\pylint\plugin.py", line 29, in from spyder.plugins.pylint.confpage import PylintConfigPage File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\plugins\pylint\confpage.py", line 16, in from spyder.plugins.pylint.widgets.pylintgui import PylintWidget File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\plugins\pylint\widgets\pylintgui.py", line 37, in from spyder.plugins.pylint.utils import get_pylintrc_path File "C:\Users\ASUS\Anaconda3\lib\site-packages\spyder\plugins\pylint\utils.py", line 16, in import pylint.config File "C:\Users\ASUS\Anaconda3\lib\site-packages\pylint\config.py", line 54, in import toml ModuleNotFoundError: No module named 'toml'Versions
Dependencies
The text was updated successfully, but these errors were encountered: