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 HassanAbouelela, belopolsky, p-ganssle, steven.daprano, yurzo
Date 2020-10-14.15:49:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602690575.25.0.378094825835.issue41904@roundup.psfhosted.org>
In-reply-to
Content
I agree that having some of datetime.now([tz]) functionality replicated in datetime.today() makes little sense.  However, the presence of this method in datetime class is a consequence of datetime being a subclass of the date class. The latter was a design mistake IMO, but as other pointed out it is too late to do anything about it.
History
Date User Action Args
2020-10-14 15:49:35belopolskysetrecipients: + belopolsky, steven.daprano, p-ganssle, yurzo, HassanAbouelela
2020-10-14 15:49:35belopolskysetmessageid: <1602690575.25.0.378094825835.issue41904@roundup.psfhosted.org>
2020-10-14 15:49:35belopolskylinkissue41904 messages
2020-10-14 15:49:35belopolskycreate