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 barry, belopolsky, p-ganssle, tim.peters, vstinner
Date 2018-01-09.21:17:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515532655.3.0.467229070634.issue32522@psf.upfronthosting.co.za>
In-reply-to
Content
> (And, honestly, `dateutil` would provide a version-independent backport anyway).

Why not start with that?  Remember: python standard library is where code goes to die.  By implementing this feature in dateutil you will not be tied to relatively slow python release schedule.  Of course, you cannot change datetime.now from a 3rd party module, but you can provide your own dateutil.now with the desired features.

The only downside I see is that you will need to copy much of datetime.now implementation which is rather convoluted.
History
Date User Action Args
2018-01-09 21:17:35belopolskysetrecipients: + belopolsky, tim.peters, barry, vstinner, p-ganssle
2018-01-09 21:17:35belopolskysetmessageid: <1515532655.3.0.467229070634.issue32522@psf.upfronthosting.co.za>
2018-01-09 21:17:35belopolskylinkissue32522 messages
2018-01-09 21:17:35belopolskycreate