Repository navigation
naturaldelta with negative seconds loses precision and doesn't match naturaltime #18
Description
Activity
>>> dt.timedelta(seconds=-1) datetime.timedelta(days=-1, seconds=86399) >>> dt.timedelta(seconds=1) datetime.timedelta(seconds=1)
I also didn't expect this behavior, but
humanize.naturaldelta()matches the behavior ofdatetime.timedelta(). Or rather it's caused by the behavior ofdatetime.timedelta()? The question is whether it's correct to humanize "-1 days and 86k seconds" to "a day (ago)".One solution could be to call
abs()on thevalueparameter since a delta is neither negative or positive.abs()also works ondt.timedeltas.- changed the title
[-]Naturaldelta with negative seconds looses precision and doesn't match naturaltime[/-][+]naturaldelta with negative seconds loses precision and doesn't match naturaltime[/+]on May 19, 2022
What did you do?
I passed a small negative integer value to
naturaldelta, it reports "a day".What did you expect to happen?
I expect
naturaldeltato roughly matchnaturaltime. Else, if negative values are not supported, it should be documented.What actually happened?
shows:
What versions are you using?
Linux LCARS2 5.17.4-200.fc35.x86_64 #1 SMP PREEMPT Wed Apr 20 15:37:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux