You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pendulum interval seems incompatible with Python native datetime #906
changed the title [-]Pendulum intervals seems incompatible with Python native `datetime`[/-][+]Pendulum 'interval' seems incompatible with Python native `datetime`[/+]on Aug 1, 2025
changed the title [-]Pendulum 'interval' seems incompatible with Python native `datetime`[/-][+]Pendulum `interval` seems incompatible with Python native `datetime`[/+]on Aug 1, 2025
This appears to be some bug specifically with the in_words() function -- all the rest of the things such as total_seconds work correctly and report 345600.0 ( == 86400 * 4 = 24 * 60 * 60 * 4)
When I looked at it in more detail I realized that inconsistency in the in_words() function exists in only version 3.1. When I tested it again in development version (3.2.0.dev0), I saw that both Native DateTime and Pendulum DateTime gave correct and same results, but I couldn't figure out after which commit this issue was resolved.
@ashb@ayorgo To sum up, could you try again in 3.2.0.dev0? I think this bug has already been fixed in the development version.
Activity
[-]Pendulum intervals seems incompatible with Python native `datetime`[/-][+]Pendulum 'interval' seems incompatible with Python native `datetime`[/+][-]Pendulum 'interval' seems incompatible with Python native `datetime`[/-][+]Pendulum `interval` seems incompatible with Python native `datetime`[/+]ashb commentedon Aug 2, 2025
This appears to be some bug specifically with the
in_words()function -- all the rest of the things such astotal_secondswork correctly and report 345600.0 ( == 86400 * 4 = 24 * 60 * 60 * 4)Eren-Acar commentedon Oct 24, 2025
When I looked at it in more detail I realized that inconsistency in the
in_words()function exists in only version 3.1. When I tested it again in development version (3.2.0.dev0), I saw that both Native DateTime and Pendulum DateTime gave correct and same results, but I couldn't figure out after which commit this issue was resolved.@ashb @ayorgo To sum up, could you try again in
3.2.0.dev0? I think this bug has already been fixed in the development version.fix: precise_diff inconsistent with pendulum.DateTime subclasses