Hello, in almost all projects I work on, I end up using a JSONField. Since I value being able to run with any database, I'm not relying on django.contrib.postgres.fields.JSONField. So I have been using pypi's django-jsonfield maintained by Matthew Schinckel: https://bitbucket.org/schinckel/django-jsonfield (I have also packaged this for Debian)
I have recently discovered pypi's "jsonfield" maintained by Brad Jasper: https://github.com/bradjasper/django-jsonfield Both projects are very similar (and use the same python package name) and both projects are actually looking for a new maintainer... since I rely on something like this, I would be willing to try to merge the best of both modules into a possible django.contrib.jsonfield or directly into the core. We could use this opportunity to let the newly-integrated field use DjangoJSONEncoder by default (see recent discussion about this) and django.contrib.postgres could register its additionals lookups into the generic field (assuming we use "jsonb" as underlying type for postgresql). What do you think of this? If inclusion into Django is not desired, then maybe we could aim to at least merge both of those projects in a single "blessed" third-party module that could be maintained in https://github.com/django/django-jsonfield? Cheers, -- Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20160623095656.GB22598%40home.ouaza.com. For more options, visit https://groups.google.com/d/optout.
