[Datetime-SIG] Computing .dst() as a timedelta

Alexander Belopolsky alexander.belopolsky at gmail.com
Tue Sep 22 19:13:30 CEST 2015

On Tue, Sep 22, 2015 at 12:44 PM, Chris Angelico <rosuav at gmail.com> wrote:
> Yes! Yes, a hundred times yes! Whenever possible, I try to synchronize
> on UTC with everyone. Our Dungeons & Dragons campaigns are all
> scheduled that way - eg I run one at 2AM UTC every Sunday. It's fair
> on everyone, that way; nobody has to cope with more than one
> timezone's DST changes, and only ever their own.

I call UTC "make it equally annoying to everyone choice."   It is tolerable
within (Western) Europe, but when your team is more geographically diverse,
2AM UTC may still be Saturday for some.

Our job as programmers is to teach computers how to understand humans, not
the other way around.  A good scheduling application should allow you to
set up the schedule in any way you want including your local time, your
standard time or any other time zone that is "special" for your particular
case (Dragonlance Mean Time, perhaps:-).  Once scheduled, the times should
be displayed to your team members in their local time.  If you make a
schedule relative to a time zone with DST transitions, some of your team
members may be surprised by the apparent changes of the schedule.  That's a
human problem - whatever compromise you come up with - your computer should
be helpful in implementing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/datetime-sig/attachments/20150922/0f46808b/attachment.html>

More information about the Datetime-SIG mailing list