New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARROW-16547: [Python] to_pandas fails with FixedOffset timezones when timestamp_as_object is used #14448
Conversation
|
Ha, I am getting the strange behaviour on CI now (not locally): Edit: actually I think the expected |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
…ixes CI failures for PyObject_CallOneArg
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
The remaining failures are ones are known ones, so merging! |
Benchmark runs are scheduled for baseline = c56934b and contender = 31e8eeb. 31e8eeb is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
['Python', 'R'] benchmarks have high level of regressions. |
This PR tries to substitute
fromutc
method inConvertTimezoneAware
(arrow_to_pandas.cc) as it errors whentzinfo
is an instance ofpytz
timezone. Basically does the change from:to
but in C++.
Thank you @milesgranger for the help!