kou commented on issue #44455: URL: https://github.com/apache/arrow/issues/44455#issuecomment-2421530711
I think that this is a problem in https://www.iana.org/time-zones data. https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1056872&view=logs&j=f4756218-2105-5c4f-5cb9-a0ac2817b29f&t=9335683b-4beb-5b59-1ea3-40427499ebdb&l=44798 ```text ---------------------------- Captured stderr call ----------------------------- Rule Mexico 1931 only - April 30 0:00 1:00 D Mexico 1931 1931 Jan/01 00:00:00 00:00:00 ============================== warnings summary =============================== ``` The latest data https://data.iana.org/time-zones/releases/tzdata2024b.tar.gz includes the "April" line in `northamerica`. Other lines use `Oct`, `Feb` and so on (3 characters). `tz.cpp` assumes 3 characters month: https://github.com/apache/arrow/blob/0c3206772051c52fe2e648623daaca2c4e71cb72/cpp/src/arrow/vendored/datetime/tz.cpp#L608 But the upstream supports `April`: https://github.com/HowardHinnant/date/blob/deec054564d0950b1a70b7f54b9039e4f0fb26cf/src/tz.cpp#L664-L674 Workaround: Use old tzdata. Solution: Update bundled datetime. FYI: `tz.cpp` doesn't use tzdata (`.../zoneinfo/...`) from conda on Windows. It uses raw https://www.iana.org/time-zones data -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
