Repository navigation
min() and max() support for np.datetime and np.timedelta - #7836
Conversation
1291992 to
a305435
Compare
njriasan
left a comment
There was a problem hiding this comment.
This looks pretty good Ben. I left some comments with some changes.
In addition could you change the title of this PR. As it is right now I think the name is unclear, but I think a name like min() and max() support for np.datetime and np.timedelta makes it much easier to understand what this PR contains.
66b8e5d to
75f86bf
Compare
75f86bf to
75c23bc
Compare
njriasan
left a comment
There was a problem hiding this comment.
@benwilliamgraham I left some feedback on what I think are possible issues. Good work so far!
f8bd8d4 to
42ee62e
Compare
njriasan
left a comment
There was a problem hiding this comment.
Overall I think this looks pretty good. Have you determined the source of the CI failure?
njriasan
left a comment
There was a problem hiding this comment.
I left a couple of comments but it looks very close. Thank you Ben!
Co-authored-by: Nick Riasanovsky <njriasanovsky@berkeley.edu>
Co-authored-by: Nick Riasanovsky <njriasanovsky@berkeley.edu>
njriasan
left a comment
There was a problem hiding this comment.
LGMT @benwilliamgraham. Thank you!
|
@stuartarchibald could you have the label switched from "in progress" to "ready for review" please? |
9ba50cc to
7b0e387
Compare
|
@benwilliamgraham thank you for working on this, your efforts to improve Numba are appreciated. A quick note about force-pushes. In general, we discourage contributors to force push after a review has begun. This is because our experience has shown, that this makes it harder for Github to line up the comments and also makes it harder for reviewers to follow what has been changed etc.. Thank you in advance for complying with this practice! 🙏 |
|
@esc Is it possible to get this added to the 0.56 milestone? |
Co-authored-by: Siu Kwan Lam <1929845+sklam@users.noreply.github.com>
Fix for #4134