You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.
Getting the following DeprecationWarning notices when I run runserver on my Django 1.3 app with the latest version of Gargoyle installed (tried both through pip install and straight from github):
/usr/local/lib/python2.6/dist-packages/django/db/models/fields/subclassing.py:80: DeprecationWarning: A Field class whose get_db_prep_save method hasn't been updated to take a `connection` argument.
new_class = super(SubfieldBase, cls).__new__(cls, name, bases, attrs)
/usr/local/lib/python2.6/dist-packages/django/db/models/fields/subclassing.py:80: DeprecationWarning: A Field class whose get_db_prep_value method hasn't been updated to take `connection` and `prepared` arguments.
new_class = super(SubfieldBase, cls).__new__(cls, name, bases, attrs)
The text was updated successfully, but these errors were encountered:
I found this too. I tried to swap in a different django-jsonfield module only to realise that it is actually incompatible (wishful thinking I guess!). Although I realised that after I submitted this pull request.
The long and the short of it is that this looks to be caused by the originaldjango-jsonfield and there is an issue for this already.
i had this very same error using gargoyle with django 1.4 (as gargoyle is using django-jsonfield==0.6)
Upgrading to django-jsonfield 0.8.5 seems to have resolved this, and makes (i'll keep this ticket in touch if anything happens) gargoyle compatible with django 1.4
Enjoy :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Getting the following DeprecationWarning notices when I run runserver on my Django 1.3 app with the latest version of Gargoyle installed (tried both through pip install and straight from github):
The text was updated successfully, but these errors were encountered: