Make NAV compatible with Django 1.7
Bug #1248195 reported by
Ole Martin Bjørndalen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Medium
|
Morten Brekkevold |
Bug Description
python/
Django 1.4 is old, and a new Debian release has been frozen with Django 1.7 in it.
We should target Django 1.7, likely for NAV 4.3, but simultaneous compatibility with version 1.5 and 1.6 is desirable, if at all possible.
Changed in nav: | |
importance: | Low → Medium |
status: | Triaged → In Progress |
summary: |
- NAV is incompatible with Django 1.5 through 1.7 + Make NAV compatible with Django 1.7 |
Changed in nav: | |
milestone: | 4.3.0 → 4.4.0 |
Changed in nav: | |
assignee: | Christian Strand Young (lizter) → Morten Brekkevold (mbrekkevold) |
Changed in nav: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I don't think this is the only thing that prevents NAV from running on Django 1.5.
NAV will likely target Django 1.4 for at least another year, basically until Debian 8 comes out. It doesn't hurt if we can write code to be compatible with both Django 1.4 and newer versions, though. It will ease the transition when we get there.