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 p-ganssle
Recipients belopolsky, p-ganssle, tim.peters, vstinner
Date 2018-01-09.16:09:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515514164.26.0.467229070634.issue32522@psf.upfronthosting.co.za>
In-reply-to
Content
@Victor: With regards to getting a "date as datetime", that is another way to do it that I have also done in the past (and in fact it's how the new dateutil.utils.today() function is implemented: https://github.com/dateutil/dateutil/blob/master/dateutil/utils.py#L7), but it's still not particularly elegant and doesn't obviously convey what you want there.

And yes, I'm aware of timespec, I linked it in my original report (it was actually added in Python 3.6).
History
Date User Action Args
2018-01-09 16:09:24p-gansslesetrecipients: + p-ganssle, tim.peters, belopolsky, vstinner
2018-01-09 16:09:24p-gansslesetmessageid: <1515514164.26.0.467229070634.issue32522@psf.upfronthosting.co.za>
2018-01-09 16:09:24p-gansslelinkissue32522 messages
2018-01-09 16:09:24p-gansslecreate