Author belopolsky
Recipients ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, pitrou, rafe, vstinner
Date 2010-05-25.21:55:45
SpamBayes Score 0.0111953
Marked as misclassified No
Message-id <AANLkTim6Fxls94r92RFUynbTzOKRpRIzwQZ8SYNh8i6G@mail.gmail.com>
In-reply-to <1274823314.68.0.978113071512.issue5094@psf.upfronthosting.co.za>
Content
..
Thanks for the explanation.  I realize that I should not have used the
s-word. :-)  In fact I only wanted a module level constant utc = UTC()
and did not care much about other UTC class instances and whether any
are permitted or easy to create.

Well, the datetime module is not exactly the place you want to start
if you want to lead anyone to best Python practices. :-) (Just think
of datetime subclassing from date!)

> Now if a simple FixedOffsetTimeZone class was added and we just pre-populated the datetime module with a utc attribute that contained an
> instance of that class set to the proper values for UTC, that I could support without controversy.

This is exactly my preferred solution.
History
Date User Action Args
2010-05-25 21:55:47belopolskysetrecipients: + belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-05-25 21:55:45belopolskylinkissue5094 messages
2010-05-25 21:55:45belopolskycreate