Question

这并非始终是这一法典的空白,而是最新的。看来是随机的,任何想法?

try:
    u = User.objects.get(email__iexact=useremail)
except User.DoesNotExist:
    ...

Throws this error, randomly.

File "/srv/myapp/registration/models.py", line 23, in get_or_create_user
  u = User.objects.get(email__iexact=useremail)

File "/usr/local/lib/python2.6/dist-packages/django/db/models/manager.py", line 132, in get
  return self.get_query_set().get(*args, **kwargs)

File "/usr/local/lib/python2.6/dist-packages/django/db/models/query.py", line 349, in get
  % self.model._meta.object_name)

TypeError: ‘DoesNotExist’ object is not callable

Answer 1

正如克里斯在以上评论中所说的那样,你的狙击手是有效的。在贵国法典的其他地方,你可能会发现不正确的例外情况。

你们可能拥有这样的东西:

try:
    do_something()
except User.MultipleObjectsReturned, User.DoesNotExist:
    pass

而不是:

try:
    do_something()
except (User.MultipleObjectsReturned, User.DoesNotExist):
    pass

如无母体,则该声明的除外内容相当于 Python+中的以下内容:

except User.MultipleObjectsReturned as User.DoesNotExist:

<代码>的例子用户:MultipleObjects Retured exception overwrites User.Does NotExist。

When the same process handles a different request later on, you get the TypeError because your code is trying to call the exception instance which has replaced User.DoesNotExist.

友情链接