Django 1.10 compatibility

Question

Django 1.10 compatibility

MattFisher opened this issue 8 years ago · comments

autoslug.utils.get_uniqueness_lookups uses _meta.get_field_by_name, which is deprecated in Django 1.9 and removed in Django 1.10 (shows up when running Django 1.8 with the -Wall python flag):

.../python2.7/site-packages/autoslug/utils.py:119: RemovedInDjango110Warning: 'get_field_by_name is an unofficial API that has been deprecated. You may be able to replace it with 'get_field()'
    field_object, model, direct, m2m = instance._meta.get_field_by_name(field_name)

Artur Barseghyan · Answer 1 · Tue Sep 13 2016 17:15:56 GMT+0800 (China Standard Time)

What's the status of this?

Daniel Roy Greenfeld · Answer 2 · Sat Sep 17 2016 03:59:50 GMT+0800 (China Standard Time)

Resolved in #16, just waiting for commentary or merge by project owner.

Yacht Shaver · Answer 3 · Tue Feb 07 2017 17:41:50 GMT+0800 (China Standard Time)

Can we close this issue now ?

Artur Barseghyan · Answer 4 · Tue Feb 07 2017 20:43:45 GMT+0800 (China Standard Time)

@jpic:

I'd say, it's fixed when a new version containing the fix is released. Asking people to use master branch or certain commit it dirty.

Eduard Luca · Answer 5 · Fri May 05 2017 20:22:12 GMT+0800 (China Standard Time)

@neithere any news on this? This is really breaking Django 1.10+ compatibility. I get that you're busy on other stuff, so is there anyone else with enough privileges that can create the new version?

Justin Mayer · Answer 6 · Sat Feb 02 2019 21:50:04 GMT+0800 (China Standard Time)

django-autoslug v1.9.4, which should now support Django 1.10, 1.11, and 2.0+, has been released and published to PyPI. The documentation will be updated once ownership of the corresponding ReadTheDocs project has been transferred. (Link to transfer request)

Thanks to everyone for your patience! 🎉