Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DEP: Expire deprecation to ignore bad dtype= in logical ufuncs (#22541)
* DEP: Expire deprecation to ignore bad dtype= in logical ufuncs Basically only `bool` and `object dtype make sense, but they did not work correctly. The dtype argument was rather ignored often. The offending behavior was deprecated in 1.20 and is now removed. Co-authored-by: Sebastian Berg <sebastianb@nvidia.com> Co-authored-by: Charles Harris <charlesr.harris@gmail.com>
- Loading branch information
1 parent
9399106
commit 10908c5
Showing
5 changed files
with
26 additions
and
87 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
* The ``dtype=`` argument to comparison ufuncs is now applied | ||
correctly. That means that only ``bool`` and ``object`` are valid | ||
values and ``dtype=object`` is enforced. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters