[GH-ISSUE #160] support django 1.7 #150

New issue

Closed

opened 2026-02-26 09:36:06 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 09:36:06 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Sep 3, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/160

django 1.7 was released, we should support it (but maybe wait for bugfix release 1.7.1).

Changes / Incompatibilities see there: https://docs.djangoproject.com/en/1.7/releases/1.7/

For us, that means:

we drop python 2.6 and add python 3.4 support (as django does)
we drop support for django 1.6 (as it doesn't support py 3.4)
we remove all south migrations, continue with builtin migrations
because of migrations, it likely is a good idea for us to have no schema changes between previous release and the release containing the django 1.7 support (and new migrations system).
update our docs with all the changes (migrations, requirements, ...)

Originally created by @ThomasWaldmann on GitHub (Sep 3, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/160 django 1.7 was released, we should support it (but maybe wait for bugfix release 1.7.1). Changes / Incompatibilities see there: https://docs.djangoproject.com/en/1.7/releases/1.7/ For us, that means: - we drop python 2.6 and add python 3.4 support (as django does) - we drop support for django 1.6 (as it doesn't support py 3.4) - we remove all south migrations, continue with builtin migrations - because of migrations, it likely is a good idea for us to have no schema changes between previous release and the release containing the django 1.7 support (and new migrations system). - update our docs with all the changes (migrations, requirements, ...)