AlenkaF commented on issue #48409:
URL: https://github.com/apache/arrow/issues/48409#issuecomment-3654922887
Oh, I see
```python
In [14]: b = None
In [15]: a == b
Out[15]: False
In [16]: import pyarrow.compute as pc
In [17]: pc.equal(a,b)
Out[17]:
<pyarrow.lib.BooleanArray object at 0x12eb27340>
[
null,
null,
null
]
In [18]: bool(pc.equal(a,b))
Out[18]: True
In [19]: bool(a == b)
Out[19]: False
```
I think the first option of not falling back to the length of the array (the
NumPy "way") is cleaner though I don't really see the huge cost and annoyance
that might bring (only slight :) ). The other option, which is changing
`equals` and keeping `__eq__` as is, would also be OK with me, if we see the
need to be less disruptive.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
