New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare for Django 2.0 #320
Commits on Oct 20, 2017
-
Update models.py for Django 2.0
`field.rel.to` was deprecated since 1.9 and removed in 2.0
-
Update admin.py for Django 2.0
`django.core.urlresolvers` was deprecated since 1.10 and removed in 2.0 see https://docs.djangoproject.com/en/1.11/ref/urlresolvers/
-
Commits on Nov 28, 2017
-
Updated
is_authenticated
to be a property.`is_authenticated` has been a method until Django 1.9. Further information: https://docs.djangoproject.com/en/1.11/releases/1.10/#using-user-is-authenticated-and-user-is-anonymous-as-methods
-
Merge pull request #1 from dgilge/django2.0
Updated `is_authenticated` to be a property.
-
Commits on Dec 4, 2017
-
is_authenticated shouldn't emit a warning in Django 1.10+ anymore.
Note: In Django 2.0 the AttributeError is raised in all passing tests right now.
-
-
-
-
Merge pull request #2 from dgilge/django2.0
Further fixes for Django 2.0 contributed by @dgilge
Commits on Dec 20, 2017
-
Merge fix for Django 2.0 with new self-referential model logic
Ross Rogers committedDec 20, 2017
Commits on Dec 21, 2017
-
Correct @flesser's merge to remove new uses of
old_field.rel.to
. Re……order field check per @merwok feedback
Ross Rogers committedDec 21, 2017
Commits on Dec 22, 2017
-
Merge pull request #4 from RossRogers/django2.0
Correct merge to remove new uses of `old_field.rel.to`. Reorder field check per @merwok feedback