Customizing the encoder (or even using DjangoJSONEncoder by default) isn't so bad.
I'm less convinced about the usefulness of customizing the decoder - once you've encoded the data into JSON any additional type information is lost, so casting back to python primitives is always going to need to be handled explicitly. Being able to set field values that contain eg datetimes *could* be a useful shortcut, but it only makes sense to me if we make it clear that values passed into the JSON field will only ever be stored/retrieved as their JSON primitive representations. Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3fe79e25-bbab-484a-abd5-051e60fcc189%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
