Question

此代码在django / db / models / fields.py中创建/定义异常？

class ReverseSingleRelatedObjectDescriptor(six.with_metaclass(RenameRelatedObjectDescriptorMethods)):
    # This class provides the functionality that makes the related-object
    # managers available as attributes on a model class, for fields that have
    # a single "remote" value, on the class that defines the related field.
    # In the example "choice.poll", the poll attribute is a
    # ReverseSingleRelatedObjectDescriptor instance.
    def __init__(self, field_with_rel):
        self.field = field_with_rel
        self.cache_name = self.field.get_cache_name()

    @cached_property
    def RelatedObjectDoesNotExist(self):
        # The exception can't be created at initialization time since the
        # related model might not be resolved yet; `rel.to` might still be
        # a string model reference.
        return type(
            str('RelatedObjectDoesNotExist'),
            (self.field.rel.to.DoesNotExist, AttributeError),
            {}
        )

这是在django / db / models / fields / related.py中引发上述异常：

def __get__(self, instance, instance_type=None):
    if instance is None:
        return self
    try:
        rel_obj = getattr(instance, self.cache_name)
    except AttributeError:
        val = self.field.get_local_related_value(instance)
        if None in val:
            rel_obj = None
        else:
            params = dict(
                (rh_field.attname, getattr(instance, lh_field.attname))
                for lh_field, rh_field in self.field.related_fields)
            qs = self.get_queryset(instance=instance)
            extra_filter = self.field.get_extra_descriptor_filter(instance)
            if isinstance(extra_filter, dict):
                params.update(extra_filter)
                qs = qs.filter(**params)
            else:
                qs = qs.filter(extra_filter, **params)
            # Assuming the database enforces foreign keys, this won't fail.
            rel_obj = qs.get()
            if not self.field.rel.multiple:
                setattr(rel_obj, self.field.related.get_cache_name(), instance)
        setattr(instance, self.cache_name, rel_obj)
    if rel_obj is None and not self.field.null:
        raise self.RelatedObjectDoesNotExist(
            "%s has no %s." % (self.field.model.__name__, self.field.name)
        )
    else:
        return rel_obj

问题是这段代码：

    try:
        val = getattr(obj, attr_name)
    except related.ReverseSingleRelatedObjectDescriptor.RelatedObjectDoesNotExist:
        val = None  # Does not catch the thrown exception
    except Exception as foo:
        print type(foo)  # Catches here, not above

不会捕获该异常

>>>print type(foo)
<class 'django.db.models.fields.related.RelatedObjectDoesNotExist'>
>>>isinstance(foo, related.FieldDoesNotExist)
False

和

except related.RelatedObjectDoesNotExist:

提出AttributeError: 'module' object has no attribute 'RelatedObjectDoesNotExist'

>>>isinstance(foo, related.ReverseSingleRelatedObjectDescriptor.RelatedObjectDoesNotExist)
Traceback (most recent call last):
  File "<string>", line 1, in <fragment>
TypeError: isinstance() arg 2 must be a class, type, or tuple of classes and types

这可能就是原因。

Answer 1

如果您的相关模型名为Foo，您可以这样做：

except Foo.DoesNotExist:

当它不可怕时，Django真是太棒了。 RelatedObjectDoesNotExist是一个返回在运行时动态计算出来的类型的属性。该类型使用self.field.rel.to.DoesNotExist作为基类。根据Django文档：

ObjectDoesNotExist and DoesNotExist

例外 DoesNotExist

找不到对象时会引发 DoesNotExist 异常   查询的给定参数。 Django提供了 DoesNotExist   异常作为每个模型类的属性来标识类   无法找到的对象，并允许您捕获特定的对象   模型类 try / except 。

这是实现这一目标的神奇之处。建立模型后，self.field.rel.to.DoesNotExist是该模型不存在的例外。

Answer 2

如果您不想导入相关的模型类，您可以：

except MyModel.related_field.RelatedObjectDoesNotExist:

或

except my_model_instance._meta.model.related_field.RelatedObjectDoesNotExist:

其中related_field是字段名称。

Answer 3

要捕获此异常，您可以执行

from django.core.exceptions import ObjectDoesNotExist

try:
    # Your code here
except ObjectDoesNotExist:
    # Handle exception

Answer 4

RelatedObjectDoesNotExist异常是在运行时动态创建的。以下是ForwardManyToOneDescriptor和ReverseOneToOneDescriptor描述符的相关代码段：

@cached_property
def RelatedObjectDoesNotExist(self):
    # The exception can't be created at initialization time since the
    # related model might not be resolved yet; `self.field.model` might
    # still be a string model reference.
    return type(
        'RelatedObjectDoesNotExist',
        (self.field.remote_field.model.DoesNotExist, AttributeError),
        {}
    )

因此异常继承自<model name>.DoesNotExist和AttributeError。实际上，此异常类型的完整MRO是：

[<class 'django.db.models.fields.related_descriptors.RelatedObjectDoesNotExist'>, 
<class '<model module path>.DoesNotExist'>,
<class 'django.core.exceptions.ObjectDoesNotExist'>,
<class 'AttributeError'>,
<class 'Exception'>,
<class 'BaseException'>,
<class 'object'>]

基本要点是，您可以抓住<model name>.DoesNotExist，ObjectDoesNotExist（从django.core.exceptions导入）或AttributeError，无论您在上下文中最有意义。

Answer 5

有点晚，但对其他人有帮助。

2种处理方式。

第一：

当我们需要捕获异常时

>>> from django.core.exceptions import ObjectDoesNotExist
>>> try:
>>>     p2.restaurant
>>> except ObjectDoesNotExist:
>>>     print("There is no restaurant here.")
There is no restaurant here.

第二名： 不想处理异常时

>>> hasattr(p2, 'restaurant')
False

Answer 6

tdelaney的答案非常适合常规代码路径，但如果您需要知道如何在测试中捕获此异常：

from django.core.exceptions import ObjectDoesNotExist

...

    def testCompanyRequired(self):
        with self.assertRaises(ObjectDoesNotExist):
            employee = Employee.objects.create()

你怎么抓住这个例外？

6 个答案:

ObjectDoesNotExist and DoesNotExist