On Friday, September 20, 2013 4:40:39 PM UTC+2, Curtis Maloney wrote: > I talked with the OP [or someone who talks a _lot_ like the OP:)] >
Oh, I should meet this animal–pardon, this guy. :) And the answer is: there's no way for a matching Decoder to know when to > decode any of these types, since there's no schema available. > One of the solutions, besides storing datatype within JSON (which can still be sensible, given the extra info was already stored with the old serializer, and would allow for an extension mechanism for developers) is to just match string formats. The case for a false positive matching "_datetime(2013-09-21T09:45+1)" does exist, but will be in a minority compared to those who store datetime. I guess there is no chance of this getting into 1.6 as a default, right? Davide -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
