#22004: Allow session.modified with an explicit False value to override
SESSION_SAVE_EVERY_REQUEST
----------------------------------+--------------------------------------
Reporter: bruth | Owner:
Type: Uncategorized | Status: closed
Component: contrib.sessions | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
Your proposal could degenerate into a war of (overrides that override)+
the default behavior :/
The root cause of the problem is that Django has global settings to
control the session behavior globally. Introducing exceptions isn't a good
idea.
A better idea would be to replace all relevant SESSION_* settings with a
flexible mechanism to control when sessions are saved.
In the short term, may I suggest a hack: substitute request.session with a
mock object in that view? Would that work?
--
Ticket URL: <https://code.djangoproject.com/ticket/22004#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c26c91e3abb3ea044bd0c4bcbedee1b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
