399

I am trying to raise a Warning in Python without making the program crash / stop / interrupt.

I use the following simple function to check if the user passed a non-zero number to it. If so, the program should warn them, but continue as per normal. It should work like the code below, but should use class Warning(), Error() or Exception() instead of printing the warning out manually.

def is_zero(i):
   if i != 0:
     print "OK"
   else:
     print "WARNING: the input is 0!"
   return i

If I use the code below and pass 0 to the function, the program crashes and the value is never returned. Instead, I want the program to continue normally and just inform the user that he passed 0 to the function.

def is_zero(i):
   if i != 0:
     print "OK"
   else:
     raise Warning("the input is 0!")
   return i

I want to be able to test that a warning has been thrown testing it by unittest. If I simply print the message out, I am not able to test it with assertRaises in unittest.

3
  • 1
    How exactly do you want to notify the user? through email or SMS? cause that can be hooked up but you need to be specific. Commented Oct 8, 2010 at 15:05
  • 3
    Why don't you just print the message?
    – sje397
    Commented Oct 8, 2010 at 15:06
  • 6
    @sje397 The point is that I want to be able to test that a warning has been thrown testing it by unittest. If I simply print the message out, I am not able to do that with assertRaises in unittest. Commented Oct 8, 2010 at 15:16

4 Answers 4

588
import warnings
warnings.warn("Warning...........Message")

See the python documentation: here

1
  • 51
    And warnings.warn("blabla", DeprecationWarning) for adding a class to the kind of warning being issued
    – Shadi
    Commented Dec 30, 2019 at 12:04
268

You shouldn't raise the warning, you should be using warnings module. By raising it you're generating error, rather than warning.

5
  • 1
    Thank you very much. And how then do I test that the Warning has been thrown using unittest? I cannot use assertRaises() anymore. Commented Oct 8, 2010 at 15:14
  • @Tomas Novotny you can capture stdout and stderr, then check that the strings issued by your warning are found within.
    – wheaties
    Commented Oct 8, 2010 at 15:33
  • 26
    @Tomas: I never heard of desire to test for warning, but there is available a warnings.catch_warnings context manager that will let you do this. Commented Oct 8, 2010 at 15:33
  • 1
    @SilentGhost If it's in your code, you want to test it, no? docs.pytest.org/en/6.2.x/warnings.html#warns (though to be fair that comment is over 10 years old)
    – eric
    Commented Dec 2, 2021 at 17:58
  • 1
    This doesn't explain what to actually do. This should be the accepted answer.
    – Gulzar
    Commented Apr 28, 2022 at 7:29
118

By default, unlike an exception, a warning doesn't interrupt.

After import warnings, it is possible to specify a Warnings class when generating a warning. If one is not specified, it is literally UserWarning by default.

>>> warnings.warn('This is a default warning.')
<string>:1: UserWarning: This is a default warning.

To simply use a preexisting class instead, e.g. DeprecationWarning:

>>> warnings.warn('This is a particular warning.', DeprecationWarning)
<string>:1: DeprecationWarning: This is a particular warning.

Creating a custom warning class is similar to creating a custom exception class:

>>> class MyCustomWarning(UserWarning):
...     pass
... 
... warnings.warn('This is my custom warning.', MyCustomWarning)

<string>:1: MyCustomWarning: This is my custom warning.

For testing, consider assertWarns or assertWarnsRegex.


As an alternative, especially for standalone applications, consider the logging module. It can log messages having a level of debug, info, warning, error, etc. Log messages having a level of warning or higher are by default printed to stderr.

0
8

Just a small demonstration snippet

I was a bit puzzled how to use warnings.warn, so I provide here a short demo. Note how print("code running after warning") is executed / not executed after warnings.warn / raise UserWarning. Also warnings.warn prints the warning message only once.

>>> import warnings
>>> 
>>> warnings.warn("test warning"); print("code running after warning")
<stdin>:1: UserWarning: test warning
code running after warning
>>> 
>>> raise UserWarning('test warning'); print("code running after warning")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UserWarning: test warning
>>> 
>>> warnings.warn("test warning"); print("code running after warning")
code running after warning
2
  • What's the difference between the first and the third cases? Why there is different output?
    – Foxy Fox
    Commented Aug 8, 2022 at 11:00
  • 3
    they are the same. Tge differenec is hence, in the third case, the Warning had been raised already in the past Commented Aug 8, 2022 at 13:23

Not the answer you're looking for? Browse other questions tagged or ask your own question.