-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-36323: [Python] Fix Timestamp scalar repr error on values outside datetime range #36942
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
Conversation
|
@github-actions crossbow submit -g python |
|
Revision: 8e6def2 Submitted crossbow builds: ursacomputing/crossbow @ actions-6d5645c1ef |
|
Will there need to be anything else I need to change, or is everything all set? |
kou
left a comment
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.
+1
|
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 112f949. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them. |
…tside datetime range (apache#36942) ### Rationale for this change apache#36323 ### What changes are included in this PR? Changed the way repr is handled for TimestampScalar ### Are these changes tested? I have added a very basic test for this change to see whether it will error or not if outside the range. ### Are there any user-facing changes? The functionality of TimestampScalar's repr now uses the `strftime` function. * Closes: apache#36323 Lead-authored-by: Ashish Bailkeri <ashishbailkeri123@gmail.com> Co-authored-by: Ashish Bailkeri <47304318+aboss123@users.noreply.github.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Rationale for this change
#36323
What changes are included in this PR?
Changed the way repr is handled for TimestampScalar
Are these changes tested?
I have added a very basic test for this change to see whether it will error or not if outside the range.
Are there any user-facing changes?
The functionality of TimestampScalar's repr now uses the
strftimefunction.