> Should JSONField accept additional kwargs to customize the encoder and the > decoder?
Quick take here: That sounds like a bit too much "cleverness" to me. The most obvious issue it'd cause is putting values of one type into the field, but getting objects of a different type back. (eg datetime getting coerced into a string on the way in, and left as a string on the way out). I'd rather see the field closely map to what the underlying database field *actually* provides. -- 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/ff5892dd-a4bd-43c7-af80-1c25260873d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
