Allow django_evolution to be imported on Django 1.7+.
Review Request #7435 — Created June 17, 2015 and submitted
A number of imports have been moved or removed in Django that affected Django Evolution. While this change doesn't fix all of them, nor does it provide proper compatibility with Django 1.7+, it does at least allow the module to be imported, and takes us one small step to working with newer versions of Django.
I was able to import the module without it blowing up.
| Description | From | Last Updated |
|---|---|---|
|
Can you comment this? |
 david
|
- Change Summary:
-
Documented the compatibility code.
- Commit:
-
ac79434775fbea26e6db945b7b7c7fe879329ac31edf8084277fe52eebc9aac89d422f0ae66bc7a9
-
Tool: Pyflakes Processed Files: django_evolution/management/__init__.py django_evolution/compat/apps.py django_evolution/signature.py Ignored Files: django_evolution/compat/__init__.py Tool: PEP8 Style Checker Processed Files: django_evolution/management/__init__.py django_evolution/compat/apps.py django_evolution/signature.py Ignored Files: django_evolution/compat/__init__.py
Tool: Pyflakes Processed Files: django_evolution/management/__init__.py django_evolution/compat/apps.py django_evolution/signature.py Ignored Files: django_evolution/compat/__init__.py Tool: PEP8 Style Checker Processed Files: django_evolution/management/__init__.py django_evolution/compat/apps.py django_evolution/signature.py Ignored Files: django_evolution/compat/__init__.py