Repository navigation
MAINT/DEP: properly implement ndarray.__pos__ - #11450
Conversation
There was a problem hiding this comment.
Oops, leftover from debugging!! (I had the problem that has_not_default... doesn't work when an error is set)
|
Why was this different, historically, than |
325e0b6 to
31ac6cd
Compare
|
@mattip - I'm guessing it was just a short-cut. Certainly, |
There was a problem hiding this comment.
nit: This doesn't belong in this PR
|
Commit tag should definitely contain |
eric-wieser
changed the title
b770252 to
f13ab50
Compare
|
OK, I changed the commit message to include "DEP". |
There was a problem hiding this comment.
Typo: ambiguous.
Is this even true? It's just ill-defined (no possible meanings), not ambiguous (>1 possible meanings).
There was a problem hiding this comment.
OK, replaced with "ill-defined".
eric-wieser
left a comment
eric-wieser
left a comment
There was a problem hiding this comment.
Just drawing attention to my comment above
f13ab50 to
ac1e129
Compare
|
@eric-wieser - I addressed your comment. OK to merge? |
|
@eric-wieser could you comment on the changes you requested? @mhvk it seems a rebase is needed |
Rather than rely on +array doing that for it.
For regular arrays, we now give a deprecation warning if np.positive cannot handle it; for ndarray subclasses that override __array_ufunc__, we pass on the type error.
ac1e129 to
3207785
Compare
|
@mattip - thanks for noticing... now rebased and approved, so can go in if tests pass. |
charris
changed the title
ndarray.__pos__
3 participants
fixed #9081
For regular arrays, we now give a deprecation warning if np.positive cannot handle it; for ndarray subclasses that override array_ufunc, we pass on the type error.