Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Crashing execution
See original GitHub issueDescription
What steps will reproduce the problem?
What happens for my program when i ran my program in
Traceback
Exception in comms call get_namespace_view:
File "C:\Program Files\Spyder\pkgs\spyder_kernels\comms\commbase.py", line 315, in _comm_message
encoding='latin-1')
ModuleNotFoundError: No module named 'torch'
Versions
- Spyder version: 4.2.1
- Python version: 3.7.9
- Qt version: 5.12.10
- PyQt5 version: 5.12.3
- Operating System: Windows 10
Dependencies
# Mandatory:
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 4.0.0 (OK)
cloudpickle >=0.5.0 : 1.6.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree : None (OK)
IPython >=7.6.0 : 7.19.0 (OK)
jedi =0.17.2 : 0.17.2 (OK)
jsonschema >=3.2.0 : 3.2.0 (OK)
keyring >=17.0.0 : 21.5.0 (OK)
nbconvert >=4.0 : 6.0.7 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
paramiko >=2.4.0 : 2.7.2 (OK)
parso =0.7.0 : 0.7.0 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.7.3 (OK)
pygments >=2.0 : 2.7.3 (OK)
pylint >=1.0 : 2.6.0 (OK)
pyls >=0.36.2;<1.0.0 : 0.36.2 (OK)
pyls_black >=0.4.6 : 0.4.6 (OK)
pyls_spyder >=0.3.0 : 0.3.0 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 1.0.2 (OK)
qtconsole >=5.0.1 : 5.0.1 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.8.3 : 0.9.4 (OK)
setuptools >=39.0.0 : 51.0.0 (OK)
sphinx >=0.6.6 : 3.3.1 (OK)
spyder_kernels >=1.10.1;<1.11.0 : 1.10.1 (OK)
textdistance >=4.2.0 : 4.2.0 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog : 1.0.2 (OK)
zmq >=17 : 20.0.0 (OK)
# Optional:
cython >=0.21 : 0.29.21 (OK)
matplotlib >=2.0.0 : 3.3.3 (OK)
numpy >=1.7 : 1.19.3 (OK)
pandas >=1.1.1 : 1.1.5 (OK)
scipy >=0.17.0 : 1.5.4 (OK)
sympy >=0.7.3 : 1.7.1 (OK)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Project Crashing in Project Management: Definition & Best ...
Making a project crashing budget is the next step in executing your project crashing plan. You'll have to update your baseline, schedule and ......
Read more >Why is my add-in crashing? - Microsoft Support
Word experienced a serious problem with the 'dep exception on startup add-in' add-in. This add-in is incompatible with Data Execution Prevention mode and...
Read more >Crash (computing) - Wikipedia
In computing, a crash, or system crash, occurs when a computer program such as a software ... crashes are exploitable and let a...
Read more >Crashes - Android Developers
An app that is written using machine code or C++ crashes if there's an unhandled signal, such as SIGSEGV , during its execution....
Read more >Understanding the exception types in a crash report
Learn what the exception type tells you about why your app crashed. ... debugger the chance to interrupt the process at a specific...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, that’s really the only possible solution right now. Closing then.
Hi @ccordoba12, all the variables (even simple numpy arrays) were gone after the error in my case, so the Variable Explorer was fully empty.
I can add to this that installing spyder on exactly the same environment where PyTorch was and running Spyder on that environment solves this issue for me. Now I can explore all variables including PyTorch objects and numpy arrays.
I think this can be related to: #15683 and #15522
My environment now