Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.093 X-Spam-Evidence: '*H*': 0.82; '*S*': 0.00; 'subject:How': 0.10; 'cc:addr:python-list': 0.11; 'attached,': 0.16; 'repr': 0.16; 'timezones': 0.16; 'utc': 0.16; 'attach': 0.16; 'wrote:': 0.18; 'email addr:gmail.com>': 0.22; 'cc:addr:python.org': 0.22; 'cc:2**0': 0.24; '>': 0.26; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'message-id:@mail.gmail.com': 0.30; 'usually': 0.31; 'ago': 0.33; 'subject:time': 0.33; 'objects': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'date.': 0.36; 'shows': 0.36; 'august': 0.61; 'from:charset:utf-8': 0.61; 'first': 0.61; 'skip:\xe2 10': 0.65; 'to:addr:gmail.com': 0.65; 'default': 0.69; '8bit%:43': 0.74; 'entry,': 0.84; 'subject:location': 0.84 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=To1ph10BSOtRdFtWzWHW/0QeU8YUVxxBXtUTxQDLMUw=; b=c1OjjjspQS6WQYzeNcb5jkYWeNuCOXhXjIoqPXEeO6qntM9WRpSN7FLv3jAXKAILk1 g4P3RIfNkpYpFdC7SXY/AxORDisljApZxnt9ttW0aW8lFZYMAOJi2pVK/LotWWt5WI09 FAleXirLhO3dP2lGPap3YKWjHnDUberwD7KWClNHMO/j/cPaGm1FF5g5MMeKjbHk0rng MR/9lZ94XDwdy7pLzcSU275D4BgjI8odARTjKkTsBD06rfCo5/Q1oiB0/XgeklEsCf/6 EAgdbeuPsSFieX3XH9FjjO2S5BbSOpxxWqXGdetd8Z8RtaQePFrkgDlp9AV7vgpz3b+0 o5JQ== MIME-Version: 1.0 X-Received: by 10.50.142.68 with SMTP id ru4mr913302igb.18.1408388191317; Mon, 18 Aug 2014 11:56:31 -0700 (PDT) In-Reply-To: References: <53F14971.3010209@gmail.com> <85mwb24h9o.fsf@benfinney.id.au> <53F1875F.4020109@gmail.com> <53F1FBCC.6060406@gmail.com> Date: Mon, 18 Aug 2014 20:56:31 +0200 Subject: Re: How to look up historical time zones by date and location From: =?UTF-8?B?Q2hyaXMg4oCcS3dwb2xza2HigJ0gV2Fycmljaw==?= To: Ian Kelly Content-Type: multipart/alternative; boundary=001a11c3b784d978830500ebedab Cc: Python X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 36 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1408388194 news.xs4all.nl 2846 [2001:888:2000:d::a6]:55576 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:76503 --001a11c3b784d978830500ebedab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 18 August 2014 20:03 "Ian Kelly" 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. --=20 Chris =E2=80=9CKwpolska=E2=80=9D Warrick Sent from my SGS3. --001a11c3b784d978830500ebedab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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 th= ose
> 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 problem= atic, as there are ways to attach a ~100 years ago time zone object to a 20= 14 date.

--
Chris =E2=80=9CKwpolska=E2=80=9D Warrick <http://chriswarrick.com/>
Sent from my SGS3.

--001a11c3b784d978830500ebedab--