This was recently reported as an issue. Add a simple check to ensure
people update their dependencies as expected.
Signed-off-by: Stephen Finucane <stephen@that.guru>
Cc: Siddhesh Poyarekar <sipoyare@redhat.com>
Cc: DJ Delorie <dj@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>
"DJANGO_SETTINGS_MODULE", "patchwork.settings.production"
)
+ import django
+
+ if django.VERSION < (3, 2):
+ raise Exception('Patchwork requires Django 3.2 or greater')
+
from django.core.management import execute_from_command_line
execute_from_command_line(sys.argv)
--- /dev/null
+---
+features:
+ - |
+ The version of Django used is now checked on start-up. This can help avoid
+ issues where deployers forget to update their Django version and see odd
+ behavior as a result.