AlenkaF commented on issue #48409:
URL: https://github.com/apache/arrow/issues/48409#issuecomment-3654292833
Yes, this is a bit tricky.
I think we should first only add a deprecation warning in the docstrings of
the dunde, something like:
```python
"""
.. deprecated:: 23.0.0
The behavior of `__eq__` will change in PyArrow 25.0.0 to use
`pc.equal` kernel which handles nulls differently. To preserve
current behaviour, use the `.equals()` method explicitly.
See Also
--------
equals : Current equality behaviour (preserved method)
"""
```
and then open a separate issue (subtasks in this issue can also be used)
that will actually change the behaviour of the method after a longer
deprecation period. That is when our tests will also need to be changed.
cc @pitrou
--
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]
