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 tim.peters
Recipients Alexander.Belopolsky, Amber.Yust, Andreas.Pelme, Hanxue.Lee, Lakin.Wecker, alex, belopolsky, cvrebert, dstufft, eric.araujo, ethan.furman, georg.brandl, gwrtheyrn, lemburg, ncoghlan, pitrou, r.david.murray, shai, skip.montanaro, tim.peters, yselivanov
Date 2014-03-07.16:41:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394210489.83.0.137549369892.issue13936@psf.upfronthosting.co.za>
In-reply-to
Content
[Nick]
> - deprecate aware time() entirely (raises the thorny question of what to return from .time() on an aware datetime() object)

aware_datetime_object.time() already returns a naive time object.  The thorny question is what .timetz() should return - but if aware time objects _were_ deprecated, .timetz() itself would presumably be deprecated too.

> ... you can't easily attach a date to the time to calculate a time delta.

The class constructor datetime.combine(date_object, time_object) makes it easy to combine any two date and time objects into a datetime object.
History
Date User Action Args
2014-03-07 16:41:29tim.peterssetrecipients: + tim.peters, lemburg, skip.montanaro, georg.brandl, ncoghlan, belopolsky, pitrou, eric.araujo, alex, r.david.murray, cvrebert, Alexander.Belopolsky, ethan.furman, gwrtheyrn, Lakin.Wecker, yselivanov, shai, dstufft, Andreas.Pelme, Amber.Yust, Hanxue.Lee
2014-03-07 16:41:29tim.peterssetmessageid: <1394210489.83.0.137549369892.issue13936@psf.upfronthosting.co.za>
2014-03-07 16:41:29tim.peterslinkissue13936 messages
2014-03-07 16:41:29tim.peterscreate