Switch to timezone names instead of utc offsets

[lanjelot]

So this actually bit me last weekend during Volga, I thought I still had time left but the ctf had actually ended an hour ago. This was because in France we switched to summer daylight saving during Sat->Sun night and my profile was still set to UTC+1 on Sunday when I should have changed it to UTC+2 on Sunday morning. To address this issue, i propose we switch to timezone names.

The switch will unfortunately reset everyone's timezone setting in their profile to UTC. It is actually best to reset everyone's timezone to UTC and ask everyone to set their timezone again with the correct timezone name because we cannot possibly find out for sure the correct timezone name from the member's offset as more than one possible timezone name usually would match a specific offset. For example UTC+1 would have more than one matching candidate: Atlantic/Canary, Europe/Longon etc. (and actually wouldnt even yield Europe/Paris). The only alternative I can think of is for the dba to manually update every member's timezone offset to the most plausible timezone name based on the member's Country.

N.B:

• The module pytz actually already comes installed by default with django.
• I copy/pasted the timezone name choices from pytz.common_timezones
• The default timezone name is UTC for any new member created, and every existing member will have their timezone reset to UTC by the migration.

Thoughts?

[hugsy]

Awesome, using a proper timezone is indeed more suited.

I'll be testing soon. Thanks