I have encountered "RuntimeWarning: overflow encountered in exp ..." in my code. How do I make pyCharm break on this warning? It currently runs past it.
1
-
1Are you using numpy? You could make it raise an exception instead and find out where. stackoverflow.com/questions/10519237/… or docs.scipy.org/doc/numpy/reference/generated/numpy.seterr.htmldoctorlove– doctorlove2013-07-29 22:22:54 +00:00Commented Jul 29, 2013 at 22:22
Add a comment
|
3 Answers
I did my own research and similarly to what @doctorlove said, do
numpy.seterr(all='raise')
then numpy will raise exceptions instead of RuntimeWarnings. The exceptions can then be caught by PyCharm.
3 Comments
Shadow
I take it you didn't find a better solution to this problem? Because breakpoints stop the application, where as I would like to have it break but able to continue...
Kirill Bulygin
@shadow The exception can be caught manually since you can localize it in your code using the debugger.
PiWi
for those using scipy, there is a scipy equivalent to numpy.seterr which is scipy.special.seterr
You can use warning module to turn the warning into an error, then try-except and set break point:
import warnings
warnings.simplefilter('error')
try:
#code that generates warning
except:
#put a breakpoint here
2 Comments
Shaq
How do you remove it later? I want to catch warnings only in a specific block. I wish to add something like warnings.simplefilter('') after the except section
PiWi
for me (in PyCharm), this does not show the stack so is not very useful: there is indeed a pause at breakpoint, but with no added value.
A modification to Shuo Wang's answer:
import warnings
warnings.simplefilter('error')
try:
#code that generates warning
except:
#put a breakpoint here
pass
pass
Put the breakpoint on the pass statement that is inside the except clause. After you've reached that pass, step over it to land on the pass (which is optional, btw) that's outside the try-except block. This should allow you to see the call stack and all the variable values.
