Message 350198 - Python tracker

➜

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	michaelanckaert
Recipients	belopolsky, elinaldosoft, michaelanckaert, p-ganssle, serhiy.storchaka
Date	2019-08-22.15:35:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1566488114.41.0.0721901658233.issue37914@roundup.psfhosted.org>
In-reply-to

Content
I would support this addition. The timedelta class already has accessors for days and seconds, why not for hours and minutes? The implementation should make use of the idiomatic way as Serhiy mentioned. >>> timedelta(hours=25).seconds // 3600 1 Is wrong, it should be >>> timedelta(hours=25) // timedelta(hours=1) 25 >>> timedelta(hours=24) // timedelta(hours=1) 24

I would support this addition. The timedelta class already has accessors for days and seconds, why not for hours and minutes? 


The implementation should make use of the idiomatic way as Serhiy mentioned.  

>>> timedelta(hours=25).seconds // 3600
1

Is wrong, it should be

>>> timedelta(hours=25) // timedelta(hours=1)
25

>>> timedelta(hours=24) // timedelta(hours=1)
24

History
Date	User	Action	Args
2019-08-22 15:35:14	michaelanckaert	set	recipients: + michaelanckaert, belopolsky, serhiy.storchaka, p-ganssle, elinaldosoft
2019-08-22 15:35:14	michaelanckaert	set	messageid: <1566488114.41.0.0721901658233.issue37914@roundup.psfhosted.org>
2019-08-22 15:35:14	michaelanckaert	link	issue37914 messages
2019-08-22 15:35:14	michaelanckaert	create