Open CasperVerswijvelt opened 3 years ago
Hmm good catch. Thanks for looking into it.
This StackOverflow answer seems relevant: https://stackoverflow.com/a/21465529
I tried fixing the issue but I couldn't find where exactly I would put the suggested fix, since I'm not really the best with Django and stuff. If someone else could look at this that would be awesome.
Since DST change is coming up in most countries (september/october) it might be a good time to look into this again ...
Good point. Per https://stackoverflow.com/questions/21465528/resolving-ambiguoustimeerror-from-djangos-make-aware, it seems like this is fixed in Django 4. So perhaps the easiest solution is to just get Shynet on Django 4! (Which is something I'd like to do anyway.)
I just ran into this exact issue. After looking around in the Stack Overflow comments, a quick fix seems to be to set TIME_ZONE=UTC
. Had this at TIME_ZONE=Europe/Berlin
before.
same here, fixed with TIME_ZONE=UTC
instead of TIME_ZONE=Europe/Paris
Ugh, sorry you all had to fix this. Really I think we should just be using UTC everywhere — perhaps that's the best solution...
I'm getting an 'Error 500' when trying to visit the dashboard after a clock change for daylight savings time. Looking up the error gives me this description:
https://www.kite.com/python/docs/pytz.AmbiguousTimeError
Might look into this myself later, but wanted to report this issue asap.
Error log: