Looks like the Interval class *tries* to do the right thing by preserving the semantics of a month (and year, see below) but fails when the next/prev month doesn't have this particular day (the 31st).
So it also fails in leap years for the same reason:
>>> from roundup import date
>>> d = date.Date ('2024-02-29')
>>> d + date.Interval ('+1y')
>>> d + date.Interval ('-1y')
Turns out this may be seen as a bug of the Date / Interval implementation and not of the calendar?
Should we try to fix it there?
Looks like there are no tests for these corner cases and we might rule that the behavior was undefined before?
|2022-06-01 09:27:12||schlatterbeck||set||messageid: <firstname.lastname@example.org>|
+ schlatterbeck, rouilj|
|2022-06-01 09:27:12||schlatterbeck||link||issue2551208 messages|