Skip to content

Commit 6052505

Browse files
authored
Update DJANGO.md
1 parent 06b4797 commit 6052505

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

developers/DJANGO.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ For example, `urls.py` should really only import from `views.py` (and `utils.py`
9090
- Store Datetimes in the database in UTC.
9191
- Only convert to a specific timezone at the View/Template layer (when rendering or collectin information from the user).
9292
- Note Python has several timezone libraries that can sometimes [conflict or have performance issues](https://blog.ganssle.io/articles/2018/03/pytz-fastest-footgun.html). The fast and correct way to set a timezone of a datetime object is `dt_object.replace(tzinfo=ZoneInfo("America/Pacific"))` .
93-
93+
- Do not use the default server timezone or hardcode a timezone at any point. You should use UTC, or get the specific timezone from the domain objects (frontend UI should specify it)
9494
### Managing Environments
9595

9696
- Django should have SMTP creds, and should set the ADMINS to the back-end developer that maintains that project. Or, use sentry\_sdk with [sentry.countable.ca](sentry.countable.ca)

0 commit comments

Comments
 (0)