django-jsonfield vs jsonfield

[dmr]

I would like to use jsonfield instead of django-jsonfield which works fine once it is installed but when I install eventlog after I installed jsonfield django-jsonfield will overwrite the package. This is more of a django-jsonfield issue but I was wondering if maybe eventlog could provide an option to install jsonfield instead of django-jsonfield.

I think I would change the setup.py to include an "extra" option to use jsonfield instead. What do you think?

[paltman]

@brosner what do you think about this?

[paltman]

@brosner bump. i wonder if we could make the 2 or 3 different json field packages optional so people could use whatever they are already using. jsonfield and django-jsonfield share the same namespace, I think. Then there is django-json-field which has the same field name just a different package name.

[dmr]

The only solution I found to this problem btw is:

1. install my all dependencies (setup.py or requirements.txt)
2. uninstall both
3. install the package I want again:

pip uninstall -y jsonfield django-jsonfield
pip install jsonfield

This "solution" is bad for countless reasons but I don't know a better way. Do you?

[dmr]

"jsonfield" is now django 1.7 compatible (https://pypi.python.org/pypi/jsonfield Version 1.0.0) --> Why does eventlog use django-jsonfield and not jsonfield?

[ossanna16]

Any further discussion on this?

[rizumu]

@paltman Since Django 1.9 now has a built in jsonfield, that should be used going forward. Probably we should close this issue and begin updating any apps to use the 1.9 built-in with a ported fallback for < 1.9?

[aijogja]

Related to jsonfield. How to use query filter by jsonfield?
I need to query log data that extra field contains "title":"ADDED". Is it possible?

Thanks

[paltman]

eventlog is now using jsonfield