#31962: Raise a more appriopriate exception when session cannot be updated.
--------------------------------------+------------------------------------
Reporter: Alex Vandiver | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.sessions | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by felixxm):
* has_patch: 1 => 0
* type: Uncategorized => Cleanup/optimization
* easy: 1 => 0
* stage: Unreviewed => Accepted
Comment:
`SuspiciousSession` is better than `SuspiciousOperation`, but it's not a
big improvement because this error is not really caused by user and there
is nothing suspicious in it (see #27363). I think we should use a new
exception class as
[https://github.com/django/django/pull/7431#discussion_r85209451 proposed
in the original PR].
--
Ticket URL: <https://code.djangoproject.com/ticket/31962#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8cf329ce04723c12e593c0d19fcc55af%40djangoproject.com.
