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, cheryl.sabella, eric.smith, francismb, jbatista, joar, maker, p-ganssle, petri.lehtinen, r.david.murray, ronaldoussoren, skip.montanaro, thezulk
Date 2019-04-12.14:06:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I am pretty neutral on this. I don't think it will be terribly difficult to implement or maintain this, and while there are a few possible behaviors, if you think about it for a bit, addition with overflow behavior *does* seem like the natural way to implement it.

That said, I don't see an amazingly compelling use case for this. It's fairly rare to need to represent abstract times *at all*, and it's even more rare for performing arithmetic on those abstract times to be meaningful. I think the most dangerous aspect of this is that we might make it easier to do something that, for most people, would be the wrong thing to do.

Does anyone have some examples of real-world use cases for this, so that we're not designing in a vacuum?
Date User Action Args
2019-04-12 14:06:01p-gansslesetrecipients: + p-ganssle, skip.montanaro, ronaldoussoren, belopolsky, eric.smith, r.david.murray, maker, petri.lehtinen, francismb, thezulk, joar, jbatista, cheryl.sabella
2019-04-12 14:06:01p-gansslesetmessageid: <>
2019-04-12 14:06:01p-gansslelinkissue17267 messages
2019-04-12 14:06:00p-gansslecreate