Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #76503 > unrolled thread
| Started by | Chris “Kwpolska” Warrick <kwpolska@gmail.com> |
|---|---|
| First post | 2014-08-18 20:56 +0200 |
| Last post | 2014-08-18 20:56 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How to look up historical time zones by date and location Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2014-08-18 20:56 +0200
| From | Chris “Kwpolska” Warrick <kwpolska@gmail.com> |
|---|---|
| Date | 2014-08-18 20:56 +0200 |
| Subject | Re: How to look up historical time zones by date and location |
| Message-ID | <mailman.13111.1408388194.18130.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
On 18 August 2014 20:03 "Ian Kelly" <ian.g.kelly@gmail.com> wrote: > I also don't know why pytz shows the LMT offset in the repr for those > timezones instead of the current UTC offset. If pytz objects do not have a datetime object attached, they default to the first ever entry, which is usually LMT. This can be problematic, as there are ways to attach a ~100 years ago time zone object to a 2014 date. -- Chris “Kwpolska” Warrick <http://chriswarrick.com/> Sent from my SGS3.
Back to top | Article view | comp.lang.python
csiph-web