Skip to content

fix: interval test expectations and conversion for 365-day year - #47

Merged
adsharma merged 1 commit into
mainfrom
fix/timestamp-tz
Jul 24, 2026
Merged

fix: interval test expectations and conversion for 365-day year#47
adsharma merged 1 commit into
mainfrom
fix/timestamp-tz

Conversation

@adsharma

@adsharma adsharma commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Fixes: LadybugDB/ladybug#694

The engine Interval::getMicro fix (DAYS_PER_YEAR for whole years) has been merged to engine main (#723). Update Python bindings to match:

  • py_query_result.cpp: use DAYS_PER_YEAR (365) for whole years instead of DAYS_PER_MONTH * 12 (360)
  • _lbug_capi.py: same for all 4 C-API interval conversion sites
  • test expectations: 1082d -> 1097d, 3750d -> 3800d, 9414d -> 9544d

The engine Interval::getMicro fix (DAYS_PER_YEAR for whole years) has
been merged to engine main. Update:

- src_cpp/py_query_result.cpp: use DAYS_PER_YEAR (365) for whole years
- src_py/_lbug_capi.py: same for C-API interval conversion sites
- test/ expectations: 1082->1097 days, 3750->3800 days, 9414->9544 days
@adsharma
adsharma force-pushed the fix/timestamp-tz branch 2 times, most recently from 1ca3cc1 to 6f3b4ca Compare July 24, 2026 03:26
@adsharma
adsharma merged commit 9fc6b00 into main Jul 24, 2026
4 of 8 checks passed
@adsharma
adsharma deleted the fix/timestamp-tz branch July 24, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Timestamp and Interval (date) datatypes are not intuitively correct!?

1 participant