Clarify which session backends require django.contrib.sessions in INSTALLED_APPS
|Reported by:||Keryn Knight <django@…>||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When using cookies-based sessions django.contrib.sessions can be removed from INSTALLED_APPS setting because data is loaded from the key itself and not from the database, so there is no need for the creation and usage of django.contrib.sessions.models.Session table.
In light of that explanation, it's not clear why it is singled out as the only one that can remove django.contrib.sessions from the INSTALLED_APPS. Can any of the others? The answer is, according to the documentation ... unclear; there is a paragraph at the end of the cached sessions docs which suggests using cached_db requires following the database sessions setup, which involves having django.contrib.sessions installed. So by implication, using the cached backend (rather than the cached_db) shouldn't require following the same setup requirements. The file based caching gets such a cursory mention, it could go either way.
As part of the ticket, I think the highlighted point about the cached_db requirements ought to be a Sphinx .. note::, as it is only in reading & re-reading these docs to draft this ticket that I noticed it.
Change History (7)
comment:1 Changed 3 years ago by timo
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
- Type changed from Uncategorized to Cleanup/optimization
comment:3 Changed 3 years ago by timo
- Summary changed from Sessions backend changing could be clearer to Clarify which session backends require django.contrib.sessions in INSTALLED_APPS