- changed status to resolved
Durations with components in wrong order are parsed successfully
Issue #8
resolved
The duration parser doesn't seem to care about the order in which the durations are given:
>>> aniso8601.parse_duration('P1D1Y1M')
datetime.timedelta(396)
>>> aniso8601.parse_duration('PT1S1H')
datetime.timedelta(0, 3601)
I would expect exceptions to be raised instead.
This is with aniso8601 1.1.0.
Comments (1)
-
repo owner - Log in to comment
Fixed in 1.2.0.