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
- fix Django 1.10+ deprecation of the Manager's use_for_related_fields
by replacing with Meta.base_manager_name on the Model
- add a check for Django < 1.10 so that this maintains backward
compatibility while not giving warnings for newer versions
- (docs): change docs to note this
- (pub): add Django 2.1 classifier
Copy file name to clipboardExpand all lines: README.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,7 @@ It is expected that you already have Django installed
27
27
_This was originally used in an older Django 1.5 codebase with Python 2.7._
28
28
29
29
Should work with Django 1.4-1.9 with Python 2.7-3.x.
30
-
- Likely works with Django 1.10 and 1.11, though not 100% sure that [`._meta.fields` usage works the same way in these](https://docs.djangoproject.com/en/2.0/ref/models/meta/#migrating-old-meta-api).
31
-
- Will have some problems with Django 2.0 as the Manager's [`use_for_related_fields` has been removed](https://docs.djangoproject.com/en/2.0/releases/2.0/#features-removed-in-2-0).
30
+
- Likely works with Django 1.10-2.x, though not 100% sure that [`._meta.fields` usage works the same way in these](https://docs.djangoproject.com/en/2.0/ref/models/meta/#migrating-old-meta-api).
32
31
-`2to3` shows that there is nothing to change, so should be compatible with Python 3.x
33
32
- Likely works with Django 0.95-1.3 as well; pre 0.95, the Manager API didn't exist
34
33
- Have not confirmed if this works with earlier versions of Python.
0 commit comments