From 21e97b67dc93ebc6d3b25c0be28ed7d74a83030d Mon Sep 17 00:00:00 2001 From: Bo Lopker Date: Fri, 7 Aug 2015 12:10:22 -0700 Subject: [PATCH] Fix comment around importing exception best practices --- rest_framework/exceptions.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rest_framework/exceptions.py b/rest_framework/exceptions.py index 236087bde..af5d0b230 100644 --- a/rest_framework/exceptions.py +++ b/rest_framework/exceptions.py @@ -59,11 +59,11 @@ class APIException(Exception): # The recommended style for using `ValidationError` is to keep it namespaced -# under `serializers`, in order to minimize potential confusion with Django's +# under `exceptions`, in order to minimize potential confusion with Django's # built in `ValidationError`. For example: # -# from rest_framework import serializers -# raise serializers.ValidationError('Value was invalid') +# from rest_framework import exceptions +# raise exceptions.ValidationError('Value was invalid') class ValidationError(APIException): status_code = status.HTTP_400_BAD_REQUEST