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 yurzo
Recipients HassanAbouelela, belopolsky, p-ganssle, steven.daprano, yurzo
Date 2020-10-14.00:45:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602636355.71.0.447041375461.issue41904@roundup.psfhosted.org>
In-reply-to
Content
I searched all of github and there seem to be ~350K entries for datetime.today
I think this supports steven.daprano point against removal.

I could not spot any major library in a quick cursory look.

However I do see many calls that look a lot like they should have been

datetime.date.today rather than datetime.datetime.today.

You see people basically dropping the hours, minutes, secs.

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

I like HassanAbouelela's idea that datetime.datetime.today should return   an arbitrary fixed time rather than an arbitrary variable time.
History
Date User Action Args
2020-10-14 00:45:55yurzosetrecipients: + yurzo, belopolsky, steven.daprano, p-ganssle, HassanAbouelela
2020-10-14 00:45:55yurzosetmessageid: <1602636355.71.0.447041375461.issue41904@roundup.psfhosted.org>
2020-10-14 00:45:55yurzolinkissue41904 messages
2020-10-14 00:45:55yurzocreate