Author belopolsky
Recipients ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, pitrou, rafe, vstinner
Date 2010-06-02.22:02:09
SpamBayes Score 0.0401183
Marked as misclassified No
Message-id <AANLkTikkb8mwmV2XL53O1lsZV4li9dab9CTP3E7NqhdU@mail.gmail.com>
In-reply-to <1275513842.77.0.021274202719.issue5094@psf.upfronthosting.co.za>
Content
On Wed, Jun 2, 2010 at 5:24 PM, Brett Cannon <report@bugs.python.org> wrote:
..
> 1. Call it FixedTimezone or something (remember it has to be CapWords).

I thought consistency within module trumps PEP 8 naming standards.
The datetime module (for better or worse) uses lowercase names for its
types: date, time, datetime, tzinfo.  Shouldn't the new type follow
the suit? (This will also avoid a source of typos TimeZone vs.
TimeZone).

I don't like "fixed timezone" - it is not clear what it is fixed:
offset, geographical location or historical set of rules.  I think we
should promote the notion that timezone is just an offset.  EST is -5
hours, EDT is -4.  New York uses EST in winter and EDT in summer.   A
zoneinfo database (external to python) is a mapping from place and
time to timezone.
History
Date User Action Args
2010-06-02 22:02:13belopolskysetrecipients: + belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-06-02 22:02:10belopolskylinkissue5094 messages
2010-06-02 22:02:09belopolskycreate