Unfortunately, while we would love to remove support for Django 1.6 it
seems irresponsible to do so right now [1]. Follow up patches will add
the missing manual SQL migration along with documentation to ensure
this doesn't happen again.
[1]
This reverts commit ea050ad02c61ff1f0bd03ffb02b4706817401aee.
To allow patchwork deployment on Enterpise versions of Linux, it is
necessary to continue to support Django 1.6.
---
patchwork/settings/base.py | 7 +--
patchwork/settings/dev.py| 9 ++---
Using exceptions for flow control is bad. Be consistent and instead
use proper functions to check for version support. This also allows
the use of tools to automatically identify feature flags when
removing support for Django versions in the future.
Signed-off-by: Stephen Finucane
This reverts commit c9edb41d363b0c1926c530e8dc4c39a75e615397.
To allow patchwork deployment on Enterpise versions of Linux, it is
necessary to continue to support Django 1.6.
---
CHANGELOG.md | 4
1 file changed, 4 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index
This reverts commit 05bedc9b7678901fd6c590f32c217e1992bd290f.
To allow patchwork deployment on Enterpise versions of Linux, it is
necessary to continue to support Django 1.6.
---
tox.ini | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tox.ini b/tox.ini
index
> i == count cannot happen in the loop as i will vary from 0 to count - 1.
>
> Signed-off-by: Damien Lespiau
> ---
> patchwork/management/commands/retag.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git