Re: Proposal: local timezone-aware datetime fields in the admin site

2018-10-04 Thread Aymeric Augustin
Hello, > Do you know what OS/browser combination you were referring to with "Windows > (which, I'm afraid, has its own time zone name)"? At the system level, I'm not sure Windows is using (or was using) the timezone database (formerly known as the Olson database). I remember this being an issue

Re: Proposal: local timezone-aware datetime fields in the admin site

2018-10-04 Thread Paul Tiplady
Thanks Aymeric, A bit of digging gives: MacOS Chrome: "America/Los_Angeles" MacOS Firefox: "America/Los_Angeles" MacOS Safari: "America/Los_Angeles" Windows Edge: ""America/Los_Angeles" Do you know what OS/browser combination you were referring to with "Windows (which, I'm afraid, has its own t

Re: Proposal: local timezone-aware datetime fields in the admin site

2018-10-03 Thread Aymeric Augustin
Hello Paul, Yes, if that works, it would be great. The API you're pointing to returns a timezone name. This is better than an offset because it avoids being off by one hour when editing dates or times on the other side of the DST change. You need to check what it does on Windows (which, I'm af

Proposal: local timezone-aware datetime fields in the admin site

2018-10-03 Thread Paul Tiplady
Timezone handling in the Django admin is quite confusing for users when the users are in multiple timezones, because everything in the admin site operates in the server's time. Assuming USE_TZ=True, TIME_ZONE='UTC', USE_I18N, USE_L10N, when viewing a datetime field, users see the UTC time, with