Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #96574

Re: [Datetime-SIG] Are there any "correct" implementations of tzinfo?

Path csiph.com!news.mixmin.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!nzpost1.xs4all.net!not-for-mail
Return-Path <lac@openend.se>
X-Original-To python-list@python.org
Delivered-To python-list@mail.python.org
X-Spam-Status OK 0.003
X-Spam-Evidence '*H*': 0.99; '*S*': 0.00; 'subject:: [': 0.03; 'creighton': 0.09; 'received:openend.se': 0.09; 'received:theraft.openend.se': 0.09; 'themselves,': 0.09; 'stored': 0.10; '>on': 0.16; 'ah,': 0.16; 'design:': 0.16; 'from:addr:lac': 0.16; 'from:addr:openend.se': 0.16; 'from:name:laura creighton': 0.16; 'member)': 0.16; 'message- id:@fido.openend.se': 0.16; 'received:fido': 0.16; 'received:fido.openend.se': 0.16; 'wrote:': 0.16; 'case.': 0.18; 'found,': 0.18; 'laura': 0.18; 'subject:] ': 0.19; '2015': 0.20; 'proposed': 0.20; 'sep': 0.22; 'subject:skip:i 10': 0.22; 'mon,': 0.24; "doesn't": 0.26; '14,': 0.27; 'bad.': 0.29; 'received:se': 0.29; 'objects': 0.29; 'somebody': 0.30; 'to:name:python-list': 0.30; 'problem': 0.33; 'common': 0.33; "isn't": 0.35; 'subject:" ': 0.36; 'totally': 0.36; 'to:addr:python-list': 0.36; 'subject:?': 0.36; 'thought': 0.37; 'charset:us-ascii': 0.37; 'itself': 0.38; 'thank': 0.38; 'subject:-': 0.39; 'rather': 0.39; 'to:addr:python.org': 0.40; 'skip:u 10': 0.61; 'header:Message- Id:1': 0.61; 'identify': 0.61; 'subject:there': 0.66; 'header:In- reply-to:1': 0.84; 'subject:any': 0.84; 'absolutely': 0.88; 'subject:Are': 0.95
To "Python-List" <python-list@python.org>
From Laura Creighton <lac@openend.se>
Subject Re: [Datetime-SIG] Are there any "correct" implementations of tzinfo?
In-reply-to <1442237443.176050.383098065.12F20DB7@webmail.messagingengine.com>
References <m2h9mzqyy7.fsf@fastmail.com> <CAExdVNm0rrxhbSONfQdor7e=9t+6Tg3hh6eFq-h0NnfdpteVYg@mail.gmail.com> <1442085362.324875.381920729.5E7A6DCE@webmail.messagingengine.com> <CAExdVNnUwRKN2q=trpnD9=mxnXvuosWKO+s5=PCfjAO45-Yugw@mail.gmail.com> <CAP7h-xYFAggqbJBNCZbYFwUqCPzW7-4Rc0x_SzgAumpFYAr6oA@mail.gmail.com> <CAExdVNmfTsqunRR_b-Q1YqWrTjsV1L5ppAoAnL7SUwgR2PFU0A@mail.gmail.com> <CAP7h-xbqq2Eu+vVO2g4WmbRJ=gmL1r9D2sWhKe=qQ8Ev-n415w@mail.gmail.com> <CAP7+vJ+1Vg21qOWAD+9R2REDnWiW4o6nj=Rh8fx3x3cAZipcdw@mail.gmail.com> <CAP7h-xbA6ZagKj+rQ_cCc8d0oK1F329AAhSjY240iiDyB4756A@mail.gmail.com> <CAExdVNnw6zfJQ_wFOurjj6kcLcbr9RgXA7kvyNPmgraMcHU4vQ@mail.gmail.com> <CAP7h-xYp=MsOcvFXNCHNkXDDGH=jcAwYSSw1WWchy5bwZKjwLA@mail.gmail.com> <201509131224.t8DCOXHO004891@fido.openend.se> <CAExdVNkN465=bWeY61PFAxpiUQ-u0p2zaqtwH8PQWyQO4Jw9Mg@mail.gmail.com> <201509131600.t8DG07e0025688@fido.openend.se> <CAExdVNm3e43mJ3tqcUc9175WssV4zeuO024svJbMTjrTab=Qew@mail.gmail.com> <CAExdVNkeRVgV8CXLugMgqhUSuXU=qHYSFUo24Xw83X=8tVBjCg@mail.gmail.com> <201509140827.t8E8RPqb001076@fido.openend.se> <1442237443.176050.383098065.12F20DB7@webmail.messagingengine.com>
Comments In-reply-to Random832 <random832@fastmail.com> message dated "Mon, 14 Sep 2015 09:30:43 -0400."
MIME-Version 1.0
Content-Type text/plain; charset="us-ascii"
Content-ID <2400.1442249967.1@fido>
Date Mon, 14 Sep 2015 18:59:27 +0200
X-Greylist Sender IP whitelisted, not delayed by milter-greylist-4.3.9 (theraft.openend.se [82.96.5.2]); Mon, 14 Sep 2015 18:59:28 +0200 (CEST)
X-BeenThere python-list@python.org
X-Mailman-Version 2.1.20+
Precedence list
List-Id General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive <http://mail.python.org/pipermail/python-list/>
List-Post <mailto:python-list@python.org>
List-Help <mailto:python-list-request@python.org?subject=help>
List-Subscribe <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups comp.lang.python
Message-ID <mailman.539.1442249971.8327.python-list@python.org> (permalink)
Lines 23
NNTP-Posting-Host 2001:888:2000:d::a6
X-Trace 1442249971 news.xs4all.nl 23732 [2001:888:2000:d::a6]:44707
X-Complaints-To abuse@xs4all.nl
Xref csiph.com comp.lang.python:96574

Show key headers only | View raw


In a message of Mon, 14 Sep 2015 09:30:43 -0400, Random832 writes:
>On Mon, Sep 14, 2015, at 04:27, Laura Creighton wrote:
>> I find this totally unacceptable.  My conclusion was that hybrid tzinfo
>> objects were a _really stupid idea_ proposed by somebody who
>> misunderstood
>> the problem, or rather only understood the most common case.
>
>"Hybrid tzinfo objects" _in isolation_ are not bad. The problem isn't
>the objects themselves, it's the whole design:
>
>1. Hybrid tzinfo objects
>2. Attached tzinfo object as the _only_ way to identify the timezone of
>a datetime (no offset member)
>3. Datetime itself stored in local time.

Ah, thank you for explaining.  I thought the only reason you would
want a hybrid tzinfo number is that you absolutely did not want
an offset number.  Which is the part I found, ah, nutty.

I see now that it doesn't have to be this way.

Laura

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: [Datetime-SIG] Are there any "correct" implementations of tzinfo? Laura Creighton <lac@openend.se> - 2015-09-14 18:59 +0200

csiph-web