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, akira, belopolsky, daniel.urban, doerwalter, eric.araujo, ezio.melotti, ggenellina, kawai, l0nwlf, mark.dickinson, pitrou, r.david.murray, rafe, techtonik, tim.peters
Date 2010-07-06.15:21:37
SpamBayes Score 0.037652202
Marked as misclassified No
Message-id <1278429700.52.0.703762306655.issue9000@psf.upfronthosting.co.za>
In-reply-to
Content
I am attaching a python prototype.  I am following the convention in place for the other datetime classes of prepending the repr with 'datetime.'.  This may not be ideal, but better than to introduce an inconsistency.  The only question I think is worth considering is the representation of timezone.utc.  I would like to have repr(timezone(timedelta(0))) == 'datetime.timezone.utc' even though currently timezone(timedelta(0)) and timezone.utc are different but equal objects.  This is going to change, however.  See issue9051.

[1] http://bugs.python.org/issue5094#msg106411
History
Date User Action Args
2010-07-06 15:21:40belopolskysetrecipients: + belopolsky, tim.peters, doerwalter, mark.dickinson, ggenellina, pitrou, techtonik, ajaksu2, kawai, ezio.melotti, eric.araujo, r.david.murray, rafe, daniel.urban, l0nwlf, akira
2010-07-06 15:21:40belopolskysetmessageid: <1278429700.52.0.703762306655.issue9000@psf.upfronthosting.co.za>
2010-07-06 15:21:38belopolskylinkissue9000 messages
2010-07-06 15:21:38belopolskycreate