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.

IPython console hangs after changing warning to errors

See original GitHub issue

Description

What steps will reproduce the problem?

Run <F9> the following code:

import warnings
warnings.filterwarnings("error")

Ipython then seems to break.

Versions

Spyder version: 4.1.3
Python version: 3.7.6
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Windows 10

Dependencies


# Mandatory:
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.4.1 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
paramiko >=2.4.0               :  2.7.1 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.5.2 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.10 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.4 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.0.3 (OK)
spyder_kernels >=1.9.1;<1.10.0 :  1.9.1 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  0.29.17 (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.1 (OK)
pandas >=0.13.1                :  1.0.3 (OK)
scipy >=0.17.0                 :  1.4.1 (OK)
sympy >=0.7.3                  :  1.5.1 (OK)

Issue Analytics

State:
Created 3 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

impact27commented, Jun 12, 2020

It is not terribly surprising, if you transform warnings into errors, any warning that would be generated by the kernel gets upgraded to an error which means the kernel can crash really easily.

0reactions

ccordoba12commented, Jun 12, 2020

Thanks a lot @impact27 for your help with this one!

Top Results From Across the Web

iPython console gets totally unresponsive when using large ...

When I read large data(data format: hdf5, parquet) with pandas, ipython stops and shows "waiting for REPL." Also, even if Pycharm read the...

Ipython console in Spyder stuck on "connecting to kernel"

I have solved by uninstalling and reinstalling python(x,y) AND deleting related folders (.ipython and .spyder2) in the user folder, but I still ...

Issues closed in the 0.12 development cycle — IPython 8.6.0 ...

928: BUG: Set context for font size change shortcuts in ConsoleWidget. 901: - There is a bug when running the profiler in the...

Troubleshooting — Anaconda documentation

403 error; HTTP 000 CONNECTION FAILED; Anaconda installer download problems; Cannot open Anaconda Prompt after installation; Cannot see Anaconda menu ...

A Qt Console for IPython

This means that actions can be taken by the frontend while the Kernel is executing, or even after it crashes. The most basic...