From c94c28d65c7fc55f35d80a2dac3e3ae4200c191e Mon Sep 17 00:00:00 2001 From: Justin Iurman Date: Sun, 6 Nov 2022 06:54:19 -0500 Subject: [PATCH] chore: Eliminate use of django.utils.datetime_safe (#4698) Instead of replacing `datetime_safe` by the standard api, just remove that part of the code (because it is unused). Fixes #4513 --- ietf/meeting/models.py | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/ietf/meeting/models.py b/ietf/meeting/models.py index 36faef264..386451c34 100644 --- a/ietf/meeting/models.py +++ b/ietf/meeting/models.py @@ -60,16 +60,6 @@ for name in pytz.common_timezones: timezones.sort() -# this is used in models to format dates, as the built-in json serializer -# can not deal with them, and the django provided serializer is inaccessible. -from django.utils import datetime_safe -DATE_FORMAT = "%Y-%m-%d" -TIME_FORMAT = "%H:%M:%S" - -def fmt_date(o): - d = datetime_safe.new_date(o) - return d.strftime(DATE_FORMAT) - class Meeting(models.Model): # number is either the number for IETF meetings, or some other # identifier for interim meetings/IESG retreats/liaison summits/...