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

Chris Angelico rosuav at gmail.com
Tue Sep 22 18:44:38 CEST 2015

On Wed, Sep 23, 2015 at 2:12 AM, M.-A. Lemburg <mal at egenix.com> wrote:
> On planes, the situation seems to be similar. I've not been on a flight
> yet where the captain announces new time zones midway :-)

Me neither. Usually what I see is "Time at origin" and "Time at
destination", and occasionally a few other time points, but nobody
really cares about "time right underneath us".

> Perhaps we should just standardize on UTC world-wide and then
> instead have the work day begin at different times depending
> on location. Crazy idea, but then it'd safe us all a lot of
> work :-)

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.


More information about the Datetime-SIG mailing list