From b6a791511fc9edc68910096777f194b9d6e0b3e9 Mon Sep 17 00:00:00 2001
From: Jennifer Richards <jennifer@staff.ietf.org>
Date: Fri, 19 May 2023 12:52:26 -0300
Subject: [PATCH] chore: Use DjangoDivFormRenderer to opt in to new default

---
 ietf/settings.py | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/ietf/settings.py b/ietf/settings.py
index 039b069f8..5eed23097 100644
--- a/ietf/settings.py
+++ b/ietf/settings.py
@@ -113,6 +113,11 @@ USE_L10N = False
 USE_TZ = True
 USE_DEPRECATED_PYTZ = True  # supported until Django 5
 
+# The DjangoDivFormRenderer is a transitional class that opts in to defaulting to the div.html
+# template for formsets. This will become the default behavior in Django 5.0. This configuration
+# can be removed at that point.
+# See https://docs.djangoproject.com/en/4.2/releases/4.1/#forms
+FORM_RENDERER = "django.forms.renderers.DjangoDivFormRenderer"
 
 # Default primary key field type to use for models that don’t have a field with primary_key=True.
 # In the future (relative to 4.2), the default will become 'django.db.models.BigAutoField.'