Update Django to 4.2 LTS

Django 3.2 reaches EOL at the end of this month. I could have sworn I'd
upgraded to Django 4.2 long ago, but apparently not. Whoops.

`USE_L10` is true by default, and is no longer honored in Django 5.

Moving off the deprecated `STATICFILES_STORAGE` setting to the
now-recommend `STORAGE` setting broke the post-processing steps to
`collectstatic` without having first upgraded to `django-pipeline`
version 3.

Author: DavidCain

poetry.lock

@@ -144,7 +144,7 @@ authors = ["David Cain <[email protected]>"]
 python = "^3.10.0"
 
 [tool.poetry.group.prod.dependencies]
-Django = "^3.2"
+Django = "^4.2"
 PyJWT = ">= 2.0.0"  # 2.0.0 changed the return type of `jwt.encode()`
 beautifulsoup4 = "*"
 celery = "^5.1"

pyproject.toml

@@ -28,9 +28,3 @@
 
 # Use the fast (but wildly insecure) MD5 to speed up tests.
 PASSWORD_HASHERS = ["django.contrib.auth.hashers.MD5PasswordHasher"]
-
-# We won't run `collectstatic` before executing tests.
-# `strict_manifest` doesn't seem to stop ValueError from being raised on non-found assets.
-# As a workaround, just use the default storage instead.
-# TODO: Figure out what's going on here, ideally after moving off django-pipeline
-STATICFILES_STORAGE = "django.contrib.staticfiles.storage.StaticFilesStorage"

ws/conf/test_settings.py

@@ -59,7 +59,14 @@
 STATIC_URL = "/static/"
 STATIC_ROOT = os.getenv("STATIC_ROOT", os.path.join(BASE_DIR, "static"))
 
-STATICFILES_STORAGE = "ws.storage.ManifestStorage"
+STORAGE = {
+    "default": {
+        "BACKEND": "django.core.files.storage.FileSystemStorage",
+    },
+    "staticfiles": {
+        "BACKEND": "ws.storage.ManifestStorage",
+    },
+}
 
 STATICFILES_DIRS = [
     # For the legacy frontend, just put all the files directly in static root
@@ -318,7 +325,6 @@
 LANGUAGE_CODE = "en-us"
 TIME_ZONE = "America/New_York"
 USE_I18N = True
-USE_L10N = True
 USE_TZ = True
 
 # Participants must update their profile information every ~6 months