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 steven.daprano
Recipients HassanAbouelela, belopolsky, p-ganssle, steven.daprano, yurzo
Date 2020-10-14.01:39:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20201014013902.GS3669@ando.pearwood.info>
In-reply-to <1602636355.71.0.447041375461.issue41904@roundup.psfhosted.org>
Content
On Wed, Oct 14, 2020 at 12:45:55AM +0000, Damian Yurzola wrote:

> And you also see people doing date math on datetime.date.today which 
> will result in different answers through out the day.

Yes? Is this a problem? If I ask the question "How long is it until 
Christmas?" the answer should be different if I ask on one minute past 
midnight on December 24 or one minute to midnight.

I daresay that you are correct that many (maybe a majority) of uses of 
datetime.today are conceptually better as date.today, but not all of 
them.

> I like HassanAbouelela's idea that datetime.datetime.today should 
> return an arbitrary fixed time rather than an arbitrary variable time.

But it's not an arbitrary variable time. It is just a high-resolution 
(down to the microsecond) version of "today", instead of the 
low-resolution (down to a single day) date.today.
History
Date User Action Args
2020-10-14 01:39:31steven.dapranosetrecipients: + steven.daprano, belopolsky, p-ganssle, yurzo, HassanAbouelela
2020-10-14 01:39:31steven.dapranolinkissue41904 messages
2020-10-14 01:39:31steven.dapranocreate