Django's issue tracker uses timezone CDT

[Jacob Rief]

This presumably is a legacy from the days when Adrian Holovaty and

Jacob Kaplan-Moss started the Django project in Kansas City.

The Django issue tracker uses the timezone CDT which is correct for central Americas,

but since Django became a world wide project, in my opinion this should either

be UTC, or if possible, the browser's local time.

Is there any reason, why this never has been adjusted?

– Jacob

[Tom Carrick]

While moving the default to UTC is probably a good idea - you can change this for yourself in Preferences -> Localization.

Tom

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9d952402-1efd-419e-b4a5-0f8635c1ac73n%40googlegroups.com.

[Adam Johnson]

I'd be +1 on moving the default to UTC.

Or we could change Trac to pick up the browser's timezone offset and display datetimes accordingly.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHoz%3DMaOq8Hj_8hnjdM%3D9to6mRSQLppZ5oHWJjQ9CA8H%3Dsqq6Q%40mail.gmail.com.

[Jacob Rief]

On Monday, August 9, 2021 at 12:10:51 PM UTC+2 Adam Johnson wrote:

I'd be +1 on moving the default to UTC.

Or we could change Trac to pick up the browser's timezone offset and display datetimes accordingly.

The latter world be the cleanest solution. I'm not familiar with Trac's template rendering engine, but in my opinion the timestamp shall be rendered as ISO-timestamp in UTC and then be converted to the browsers local timezone using a JS one-liner.