By Nelson

2009-08-23 21:29:29 8 Comments

What's the proper way to declare custom exception classes in modern Python? My primary goal is to follow whatever standard other exception classes have, so that (for instance) any extra string I include in the exception is printed out by whatever tool caught the exception.

By "modern Python" I mean something that will run in Python 2.5 but be 'correct' for the Python 2.6 and Python 3.* way of doing things. And by "custom" I mean an Exception object that can include extra data about the cause of the error: a string, maybe also some other arbitrary object relevant to the exception.

I was tripped up by the following deprecation warning in Python 2.6.2:

>>> class MyError(Exception):
...     def __init__(self, message):
...         self.message = message
>>> MyError("foo") DeprecationWarning: BaseException.message has been deprecated as of Python 2.6

It seems crazy that BaseException has a special meaning for attributes named message. I gather from PEP-352 that attribute did have a special meaning in 2.5 they're trying to deprecate away, so I guess that name (and that one alone) is now forbidden? Ugh.

I'm also fuzzily aware that Exception has some magic parameter args, but I've never known how to use it. Nor am I sure it's the right way to do things going forward; a lot of the discussion I found online suggested they were trying to do away with args in Python 3.

Update: two answers have suggested overriding __init__, and __str__/__unicode__/__repr__. That seems like a lot of typing, is it necessary?


@Yaroslav Nikitenko 2019-06-10 20:40:04

See a very good article "The definitive guide to Python exceptions". The basic principles are:

  • Always inherit from (at least) Exception.
  • Always call BaseException.__init__ with only one argument.
  • When building a library, define a base class inheriting from Exception.
  • Provide details about the error.
  • Inherit from builtin exceptions types when it makes sense.

There is also information on organizing (in modules) and wrapping exceptions, I recommend to read the guide.

@logicOnAbstractions 2019-10-05 18:09:39

This is a good example of why on SO I usually check the most upvoted answer, but the most recent ones as well. Usefull addition, thanks.

@fameman 2018-11-25 17:14:25

As of Python 3.8 (2018,, the recommended method is still:

class CustomExceptionName(Exception):
    """Exception raised when very uncommon things happen"""

Please don't forget to document, why a custom exception is neccessary!

If you need to, this is the way to go for exceptions with more data:

class CustomExceptionName(Exception):
    """Still an exception raised when uncommon things happen"""
    def __init__(self, message, payload=None):
        self.message = message
        self.payload = payload # you could add more args
    def __str__(self):
        return str(self.message) # __str__() obviously expects a string to be returned, so make sure not to send any other data types

and fetch them like:

    raise CustomExceptionName("Very bad mistake.", "Forgot upgrading from Python 1")
except CustomExceptionName as error:
    print(str(error)) # Very bad mistake
    print("Detail: {}".format(error.payload)) # Detail: Forgot upgrading from Python 1

payload=None is important to make it pickle-able. Before dumping it, you have to call error.__reduce__(). Loading will work as expected.

You maybe should investigate in finding a solution using pythons return statement if you need much data to be transferred to some outer structure. This seems to be clearer/more pythonic to me. Advanced exceptions are heavily used in Java, which can sometimes be annoying, when using a framework and having to catch all possible errors.

@AuHau 2018-12-10 22:29:36

Ehm, what did the change in Python 3.8 about this? Just from curiosity, I went through the link you posted, but there is no mention of anything related to this topic...

@kevlarr 2019-03-26 16:46:13

At the very least, the current docs indicate this is the way to do it (at least without the __str__) rather than other answers that use super().__init__(...).. Just a shame that overrides for __str__ and __repr__ are probably necessary just for better "default" serializing.

@Roel Schroeven 2019-08-06 15:21:54

Honest question: Why is it important for exceptions to be pickle-able? What are the use cases for dumping and loading exceptions?

@logicOnAbstractions 2019-10-06 02:58:48

@RoelSchroeven: I had to parallelize code once. Ran fine single process, but aspects of some of its classes were not serializable (lambda function being passed as objects). Took me some time figuring it out & fixing it. Meaning someone later may end up needing your code to be serialize, be unable to do it, and have to dig up why... My issue wasn't unpickeable errors, but I can see it causing similar problems.

@Omkaar.K 2018-07-22 05:27:45

Try this Example

class InvalidInputError(Exception):
    def __init__(self, msg):
        self.msg = msg
    def __str__(self):
        return repr(self.msg)

inp = int(input("Enter a number between 1 to 10:"))
    if type(inp) != int or inp not in list(range(1,11)):
        raise InvalidInputError
except InvalidInputError:
    print("Invalid input entered")

@frnknstn 2012-04-22 18:18:17

With modern Python Exceptions, you don't need to abuse .message, or override .__str__() or .__repr__() or any of it. If all you want is an informative message when your exception is raised, do this:

class MyException(Exception):

raise MyException("My hovercraft is full of eels")

That will give a traceback ending with MyException: My hovercraft is full of eels.

If you want more flexibility from the exception, you could pass a dictionary as the argument:

raise MyException({"message":"My hovercraft is full of animals", "animal":"eels"})

However, to get at those details in an except block is a bit more complicated. The details are stored in the args attribute, which is a list. You would need to do something like this:

    raise MyException({"message":"My hovercraft is full of animals", "animal":"eels"})
except MyException as e:
    details = e.args[0]

It is still possible to pass in multiple items to the exception and access them via tuple indexes, but this is highly discouraged (and was even intended for deprecation a while back). If you do need more than a single piece of information and the above method is not sufficient for you, then you should subclass Exception as described in the tutorial.

class MyError(Exception):
    def __init__(self, message, animal):
        self.message = message
        self.animal = animal
    def __str__(self):
        return self.message

@mtraceur 2018-04-20 22:36:04

"but this will be deprecated in the future" - is this still intended for deprecation? Python 3.7 still seems to happily accept Exception(foo, bar, qux).

@frnknstn 2018-05-02 08:20:56

It haven't seen any recent work to depricate it since the last attempt failed due to the pain of transitioning, but that usage is still discouraged. I will update my answer to reflect that.

@neves 2018-05-08 17:48:42

@frnknstn, why it is discouraged? Looks like a nice idiom for me.

@frnknstn 2018-05-10 08:09:53

@neves for a start, using tuples to store exception information has no benefit over using a dictionary to do the same. If you are interested in the reasoning behind the exception changes, take a look at PEP352

@liberforce 2019-04-17 16:25:09

The relevant section of PEP352 is "Retracted Ideas".

@gahooa 2009-08-23 21:55:23

Maybe I missed the question, but why not:

class MyException(Exception):

Edit: to override something (or pass extra args), do this:

class ValidationError(Exception):
    def __init__(self, message, errors):

        # Call the base class constructor with the parameters it needs
        super(ValidationError, self).__init__(message)

        # Now for your custom code...
        self.errors = errors

That way you could pass dict of error messages to the second param, and get to it later with e.errors

Python 3 Update: In Python 3+, you can use this slightly more compact use of super():

class ValidationError(Exception):
    def __init__(self, message, errors):

        # Call the base class constructor with the parameters it needs

        # Now for your custom code...
        self.errors = errors

@jiakai 2017-08-01 02:54:22

However an exception defined like this would not be pickable; see the discussion here…

@Robino 2017-09-15 13:39:34

@jiakai means "picklable". :-)

@M. Utku ALTINKAYA 2009-08-23 21:46:54

You should override __repr__ or __unicode__ methods instead of using message, the args you provide when you construct the exception will be in the args attribute of the exception object.

@Aaron Hall 2014-11-14 21:09:22

"Proper way to declare custom exceptions in modern Python?"

This is fine, unless your exception is really a type of a more specific exception:

class MyException(Exception):

Or better (maybe perfect), instead of pass give a docstring:

class MyException(Exception):
    """Raise for my specific kind of exception"""

Subclassing Exception Subclasses

From the docs


All built-in, non-system-exiting exceptions are derived from this class. All user-defined exceptions should also be derived from this class.

That means that if your exception is a type of a more specific exception, subclass that exception instead of the generic Exception (and the result will be that you still derive from Exception as the docs recommend). Also, you can at least provide a docstring (and not be forced to use the pass keyword):

class MyAppValueError(ValueError):
    '''Raise when my specific value is wrong'''

Set attributes you create yourself with a custom __init__. Avoid passing a dict as a positional argument, future users of your code will thank you. If you use the deprecated message attribute, assigning it yourself will avoid a DeprecationWarning:

class MyAppValueError(ValueError):
    '''Raise when a specific subset of values in context of app is wrong'''
    def __init__(self, message, foo, *args):
        self.message = message # without this you may get DeprecationWarning
        # Special attribute you desire with your Error, 
        # perhaps the value that caused the error?: = foo         
        # allow users initialize misc. arguments as any other builtin Error
        super(MyAppValueError, self).__init__(message, foo, *args) 

There's really no need to write your own __str__ or __repr__. The builtin ones are very nice, and your cooperative inheritance ensures that you use it.

Critique of the top answer

Maybe I missed the question, but why not:

class MyException(Exception):

Again, the problem with the above is that in order to catch it, you'll either have to name it specifically (importing it if created elsewhere) or catch Exception, (but you're probably not prepared to handle all types of Exceptions, and you should only catch exceptions you are prepared to handle). Similar criticism to the below, but additionally that's not the way to initialize via super, and you'll get a DeprecationWarning if you access the message attribute:

Edit: to override something (or pass extra args), do this:

class ValidationError(Exception):
    def __init__(self, message, errors):

        # Call the base class constructor with the parameters it needs
        super(ValidationError, self).__init__(message)

        # Now for your custom code...
        self.errors = errors

That way you could pass dict of error messages to the second param, and get to it later with e.errors

It also requires exactly two arguments to be passed in (aside from the self.) No more, no less. That's an interesting constraint that future users may not appreciate.

To be direct - it violates Liskov substitutability.

I'll demonstrate both errors:

>>> ValidationError('foo', 'bar', 'baz').message

Traceback (most recent call last):
  File "<pyshell#10>", line 1, in <module>
    ValidationError('foo', 'bar', 'baz').message
TypeError: __init__() takes exactly 3 arguments (4 given)

>>> ValidationError('foo', 'bar').message
__main__:1: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6

Compared to:

>>> MyAppValueError('foo', 'FOO', 'bar').message

@Kos 2018-01-03 18:21:50

Hello from 2018! BaseException.message is gone in Python 3, so the critique only holds for old versions, right?

@Aaron Hall 2018-01-03 19:02:34

@Kos The critique about Liskov Substitutability is still valid. The semantics of the first argument as a "message" are also arguably questionable, but I don't think I'll argue the point. I'll give this more of a look when I have more free time.

@Jacquot 2018-03-18 23:39:33

FWIW, for Python 3 (at least for 3.6+), one would redefine the __str__ method of MyAppValueError instead of relying on the message attribute

@cowbert 2018-07-14 03:18:28

why avoid passing a dict as a positional argument? It retains all of the original semantics, including (__repr__/__str__) and the user can just parse the dict via .args[0] per frnknstn's answer? (You are noting this in the docstring aren't you?)

@ostergaard 2018-09-16 13:52:05

@AaronHall Could you expand on the benefit of sub-classing ValueError rather than Exception? You state that this is what is meant by the docs but a direct reading doesn't support that interpretation and in the Python Tutorial under User-defined Exceptions it clearly makes it the users choice: "Exceptions should typically be derived from the Exception class, either directly or indirectly." Hence keen to understand if your view is justifiable, please.

@Aaron Hall 2018-09-16 21:17:20

@ostergaard Can't answer in full right now, but in short, the user gets the additional option of catching ValueError. This makes sense if it's in the category of Value Errors. If it's not in the category of Value Errors, I'd argue against it on the semantics. There's room for some nuance and reasoning on the part of the programmer, but I much prefer specificity when applicable. I'll update my answer to better tackle the subject some time soon.

@ostergaard 2018-09-28 13:12:38

@AaronHall thanks, that does make sense and I agree. Though I believe it's a stretch to ascribe that meaning to the docs.

@mykhal 2013-08-07 16:23:56

see how exceptions work by default if one vs more attributes are used (tracebacks omitted):

>>> raise Exception('bad thing happened')
Exception: bad thing happened

>>> raise Exception('bad thing happened', 'code is broken')
Exception: ('bad thing happened', 'code is broken')

so you might want to have a sort of "exception template", working as an exception itself, in a compatible way:

>>> nastyerr = NastyError('bad thing happened')
>>> raise nastyerr
NastyError: bad thing happened

>>> raise nastyerr()
NastyError: bad thing happened

>>> raise nastyerr('code is broken')
NastyError: ('bad thing happened', 'code is broken')

this can be done easily with this subclass

class ExceptionTemplate(Exception):
    def __call__(self, *args):
        return self.__class__(*(self.args + args))
# ...
class NastyError(ExceptionTemplate): pass

and if you don't like that default tuple-like representation, just add __str__ method to the ExceptionTemplate class, like:

    # ...
    def __str__(self):
        return ': '.join(self.args)

and you'll have

>>> raise nastyerr('code is broken')
NastyError: bad thing happened: code is broken

@Lennart Regebro 2009-08-23 21:58:47

No, "message" is not forbidden. It's just deprecated. You application will work fine with using message. But you may want to get rid of the deprecation error, of course.

When you create custom Exception classes for your application, many of them do not subclass just from Exception, but from others, like ValueError or similar. Then you have to adapt to their usage of variables.

And if you have many exceptions in your application it's usually a good idea to have a common custom base class for all of them, so that users of your modules can do

except NelsonsExceptions:

And in that case you can do the __init__ and __str__ needed there, so you don't have to repeat it for every exception. But simply calling the message variable something else than message does the trick.

In any case, you only need the __init__ or __str__ if you do something different from what Exception itself does. And because if the deprecation, you then need both, or you get an error. That's not a whole lot of extra code you need per class. ;)

@Yaroslav Nikitenko 2019-06-10 20:05:14

It's interesting that Django exceptions don't inherit from a common base.‌​s Do you have a good example when catching all exceptions from a specific application is needed? (maybe it is useful only for some specific types of applications).

@Yaroslav Nikitenko 2019-06-10 20:44:29

I found a good article on this topic, . I think that Exceptions should be subclassed primarily domain-based, not application-based. When your app is about HTTP protocol, you derive from HTTPError. When part of your app is TCP, you derive that part's exceptions from TCPError. But if your app spans a lot of domains (file, permissions, etc), the reason to have a MyBaseException diminishes. Or is it to protect from 'layer violation'?

Related Questions

Sponsored Content

12 Answered Questions

[SOLVED] What's the canonical way to check for type in Python?

  • 2008-09-30 11:00:10
  • Herge
  • 818166 View
  • 1207 Score
  • 12 Answer
  • Tags:   python types

22 Answered Questions

[SOLVED] Is there a way to create multiline comments in Python?

24 Answered Questions

[SOLVED] Pythonic way to create a long multi-line string

13 Answered Questions

[SOLVED] How do you test that a Python function throws an exception?

7 Answered Questions

[SOLVED] Manually raising (throwing) an exception in Python

  • 2010-01-12 21:07:40
  • 1645338 View
  • 2139 Score
  • 7 Answer
  • Tags:   python exception

25 Answered Questions

[SOLVED] Is there a way to run Python on Android?

9 Answered Questions

[SOLVED] python exception message capturing

7 Answered Questions

14 Answered Questions

[SOLVED] Proper way to use **kwargs in Python

  • 2009-07-08 14:45:53
  • Kekoa
  • 361802 View
  • 418 Score
  • 14 Answer
  • Tags:   python kwargs

20 Answered Questions

[SOLVED] jQuery Ajax error handling, show custom exception messages

Sponsored Content