Reusing Django Apps In Own Project Which Require A Lower Django Version
Solution 1:
OK, thanks for all the comments. You helped me to answer my questions and to improve my basic understanding. Not all of the comments to my questions are 100% correct. I have to stress that Django minor releases are all backwards compatibel unless otherwise stated in the release notes and except the deprecations. Please read Django release process.
So basically all code written for Django 1.4.5 or 1.5.5 should still run under Django 1.6, and you should also be able to mix it. So it is possible to write a Django 1.6 app, reuse one 1.4.5 app and one 1.5.5 app as long as you run it in a Django version 1.6<=version<2.0.
The issue in my case was editlive defining its dependency to Django>=1.3,<=1.4.5 which caused the setup tool to download and install Django 1.4.5 onto my system. What I did not realize is that my own application started to use Django 1.4.5 from that point on. The error thrown afterwards was due to the usage of django.utils.log.RequireDebugTrue
in my own app. This filter was only introduced in Django 1.5 and thus would not run under 1.4.5.
I just had to delete the entire 1.4.5 egg directory and voila, everything works again.
I did not test the functionality of editlive yet, but at least there aren't any errors at 'compile time'.
Post a Comment for "Reusing Django Apps In Own Project Which Require A Lower Django Version"