summaryrefslogtreecommitdiff
path: root/doc/release
diff options
context:
space:
mode:
authormattip <matti.picus@gmail.com>2019-11-06 14:27:50 -0700
committermattip <matti.picus@gmail.com>2019-11-06 14:27:50 -0700
commite6a9c112bd3c08bfc4e51fa3c5345c0085c314ab (patch)
treee9ade33691d9801c996f6f6c1f65b9059ebfdf54 /doc/release
parent480dc6bc01aa465389fcad0c85502d25d954f579 (diff)
downloadnumpy-e6a9c112bd3c08bfc4e51fa3c5345c0085c314ab.tar.gz
MAINT: revert gh-14800, which gave precedence to OO->O over OO->?
Diffstat (limited to 'doc/release')
-rw-r--r--doc/release/upcoming_changes/14800.improvement.rst14
1 files changed, 0 insertions, 14 deletions
diff --git a/doc/release/upcoming_changes/14800.improvement.rst b/doc/release/upcoming_changes/14800.improvement.rst
deleted file mode 100644
index 158c31536..000000000
--- a/doc/release/upcoming_changes/14800.improvement.rst
+++ /dev/null
@@ -1,14 +0,0 @@
-Comparison on ``object`` dtypes will prefer ``object`` output
--------------------------------------------------------------
-Comparison ufuncs (``np.equal`` and friends) would return boolean arrays when
-the input array dtype was ``object``. This led to inconsistent behaviour for
-ragged arrays ``a = np.array([1, np.array([1, 2, 3])], dtype=object)``. This
-will now return an object array::
-
- >>> a = np.array([1, np.array([1, 2, 3])], dtype=object)
- >>> np.equal(a, a)
- array([True, array([ True, True, True])], dtype=object)
-
-The old behaviour, which will raise a ``ValueError`` in this case, is still
-available by specifying a dtype as ``np.equal(a, a, dtype=bool)``.
-