Django 1.10 compatibility, removed Django 1.9 warnings #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
January 12, 2016 11:32
…ecated and will be removed in Django 1.10. Update your urlpatterns to be a list of django.conf.urls.url() instances instead." warning and added compatibility to Django 1.10.
| from django.db.models import loading | ||
| loading.cache.loaded = False | ||
| except ImportError: # Django >= 1.9 | ||
| pass |
There was a problem hiding this comment.
One question about this part: does that mean that in Django 1.9 a cache clear is no longer needed?
vdboor
added a commit
that referenced
this pull request
Feb 11, 2016
Django 1.10 compatibility, removed Django 1.9 warnings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed "RemovedInDjango110Warning: django.conf.urls.patterns() is deprecated and will be removed in Django 1.10. Update your urlpatterns to be a list of django.conf.urls.url() instances instead." warning and added compatibility to Django 1.10.
All warnings in Django 1.9 have been fixed.