#21124: Default session data serializer doesn't support extended data types
----------------------------------+--------------------------------------
Reporter: sorcio@… | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: 1.6-beta-1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by victor@…):
* status: closed => new
* needs_docs: 0 => 1
* resolution: wontfix =>
* needs_tests: 0 => 1
Comment:
Hey, I also ran into this issue that broke quite huge apps such as django-
allauth and its entire oauth2 feature. Took me hours and hours to find out
that the session cache was not serializing well - there was no clue
whatsoever.
In a nutshell, deep down django-allauth puts objects such as ['foo'] (a
list of one string) in the session cache; when it's read again, it's been
transformed to 'foo' (no more list). No exception, or warning of any sort
- I guess that's the real issue, right ?
I'm not sure about how to cope with this, but there are several ways:
maybe communicate more on this change, add some tests (I place X in
session data, I retrieve X, not Y) and probably exceptions if trying to
store something unsupported.
--
Ticket URL: <https://code.djangoproject.com/ticket/21124#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.195e76ca664d22921fddd65fdd15caaf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
