On Friday, September 20, 2013 3:52:30 PM UTC+2, Davide Rizzo wrote: > > On Friday, September 20, 2013 2:55:33 PM UTC+2, Florian Apolloner wrote: >> >> Btw could it be that you are mixing out Encoder and Serializer? >> > > No, I say Serializer when I mean... well, a serializer, as specified by > SESSION_SERIALIZER. I say Encoder when I mean the Encoder class used by > JSONSerializer. It could be the one built into the json module, or it could > be a derived one, such as DjangoJSONEncoder here > https://github.com/django/django/blob/1.6b4/django/core/serializers/json.py#L79 >
Ok, I though as much, but wanted to be sure. It's either to change the default to PickleSerializer > Most likely not gonna happen since we choose secure by default. or to mitigate the JSONSerializer issue supporting these data types: > > - datetime, timedelta objects (supported by DjangoJSONEncoder) > - decimal objects (supported by DjangoJSONEncoder) > - arbitrary binary strings (b'\xe8') > - Geometry objects > > I could live with using DjangoJSONEncoder, but support for arbitrary binary strings and geometry objects would have to come via that instead of beeing specialized for sessions. That said, it's quite late for 1.6, so the patch would have to be rocksolid and would require agreement of the rest of the core devs. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
