This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients ajaksu2, belopolsky, brett.cannon, doerwalter, eric.araujo, ggenellina, kawai, pitrou, rafe, vstinner
Date 2010-05-25.16:23:09
SpamBayes Score 0.00048665307
Marked as misclassified No
Message-id <>
In-reply-to <1274780715.3174.7.camel@localhost.localdomain>
On Tue, May 25, 2010 at 5:45 AM, Antoine Pitrou <> wrote:
> I also agree with Brett that a singleton looks rather unnecessary (it
> also look quite C++/Java-esque to me).

I still don't understand your aversion to singletons and you did not
address any of the advantages that I listed in my previous comment.  I
don't think singletons are foreign to Python: after all we write None
rather than NoneType() .

We can reach a middle ground by interning UTC instances behind the
scenes so that UTC() is UTC() will always be true.  This will address
most of the issues that I raised and utc = datetime.UTC() is simple
enough to write as long as you don't have to worry about sharing utc
instance between modules.
Date User Action Args
2010-05-25 16:23:11belopolskysetrecipients: + belopolsky, doerwalter, brett.cannon, ggenellina, pitrou, vstinner, ajaksu2, kawai, eric.araujo, rafe
2010-05-25 16:23:10belopolskylinkissue5094 messages
2010-05-25 16:23:09belopolskycreate