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, eric.smith, martin.panter, p-ganssle, tebeka
Date 2020-07-20.17:15:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1595265348.42.0.0519645557346.issue41254@roundup.psfhosted.org>
In-reply-to
Content
I think it is unlikely that we'll want to experiment with this directly in CPython. I don't think a fixed format (other than the annoying one that you already get from calling `str` on a timedelta) is appropriate, but designing a modular format for time differences is more complicated than it might seem. I have had an open issue on dateutil to implement this for ages, but I haven't seen or come up with any proposals for a DSL for specifying timedelta formats: https://github.com/dateutil/dateutil/issues/444

It is annoyingly complicated to do this, and I'd rather it be tried out in other libraries with more flexibility to make breaking changes and a shorter release cadence. Dateutil is a good choice, but a clear and thorough proposal (or at least examples of this done well in other ecosystems we can crib from) is necessary.
History
Date User Action Args
2020-07-20 17:15:48p-gansslesetrecipients: + p-ganssle, tebeka, belopolsky, eric.smith, martin.panter
2020-07-20 17:15:48p-gansslesetmessageid: <1595265348.42.0.0519645557346.issue41254@roundup.psfhosted.org>
2020-07-20 17:15:48p-gansslelinkissue41254 messages
2020-07-20 17:15:47p-gansslecreate