diff options
| author | Daniel Schadt <kingdread@gmx.de> | 2022-07-16 22:30:47 +0200 |
|---|---|---|
| committer | Daniel Schadt <kingdread@gmx.de> | 2022-07-16 22:30:47 +0200 |
| commit | a07ca7c0b7e567f2647d13f84db6aed201cde56c (patch) | |
| tree | fa9891caa74745d7a4e69e955f97851e30991629 /doc/developer/localize.rst | |
| parent | 42cb1aff20b310c934be31491061c51e81dde35c (diff) | |
| download | fietsboek-a07ca7c0b7e567f2647d13f84db6aed201cde56c.tar.gz fietsboek-a07ca7c0b7e567f2647d13f84db6aed201cde56c.tar.bz2 fietsboek-a07ca7c0b7e567f2647d13f84db6aed201cde56c.zip | |
remove MyTourbook timezone guessing
It turns out that the mt:TourStartTime is also given in UTC, and
therefore cannot be used to get the timezone offset. The problem was
that my local computer's timezone was the same as the tour timezone, so
by the magic of Python's datetime.datetime.fromtimestamp (and the date
CLI util), I did not notice that the timestamp actually represents UTC.
Sadly, it currently looks like there is no way to extract the time zone
from a MyTourbook export.
Diffstat (limited to 'doc/developer/localize.rst')
0 files changed, 0 insertions, 0 deletions