anxkhn commented on PR #50368:
URL: https://github.com/apache/arrow/pull/50368#issuecomment-5095364791
the verbose pandas-latest failure shows this is a resolution mismatch, not a
timezone-data mismatch: pandas produced `2015-03-29 00:59:59.999999000z`, while
`assume_timezone` produced `2015-03-29 00:59:59.999999999z`; both used
`europe/brussels` and agreed on the offset. pandas 3.0.5 inferred the fixture
as `datetime64[us]`, but the arrow input is explicitly `timestamp[ns]`. i
pushed a one-line fix that applies `.as_unit("ns")` to the pandas fixture
before localization. `pytest -vv test_compute.py::test_assume_timezone` now
reports `1 passed` with pandas 3.0.5 and pandas 2.0.3. @rok could you please
re-review?
--
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]
