#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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"c21bbe0883772ea91993eabac6c91ff575a81912" c21bbe08]:
{{{
#!CommitTicketReference repository=""
revision="c21bbe0883772ea91993eabac6c91ff575a81912"
[3.1.x] Fixed #31864 -- Fixed encoding session data during transition to
Django 3.1.
Thanks אורי for the report.
Backport of 99abfe8f4d3caebcd73548f5bf9e4755bdfed318 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31864#comment:4>
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.4a1125949a606079311879eaf802f384%40djangoproject.com.
