#31864: Session data cannot be decoded during the transition to Django 3.1.
----------------------------------+------------------------------------
Reporter: felixxm | Owner: felixxm
Type: Bug | Status: closed
Component: contrib.sessions | Version: 3.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Carlton Gibson <carlton.gibson@…>):
In [changeset:"cdfdbb3411b7634ae119998a1d69801e1df275ff" cdfdbb34]:
{{{
#!CommitTicketReference repository=""
revision="cdfdbb3411b7634ae119998a1d69801e1df275ff"
[3.1.x] Refs #31864 -- Doc'd that DEFAULT_HASHING_ALGORITHM requires
3.1.1+ in release notes.
Backport of b2b0711b555fa292751763c2df4fe577c396f265 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31864#comment:6>
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/065.a1d4d7294c0bcd48b2e95d8e91f085dc%40djangoproject.com.
