[Numpy-discussion] Possible Deprecation of np.ediff1d

Stephan Hoyer shoyer at gmail.com
Tue Aug 28 17:05:46 EDT 2018


On Tue, Aug 28, 2018 at 12:27 PM Ralf Gommers <ralf.gommers at gmail.com>
wrote:

> On Tue, Aug 28, 2018 at 12:21 PM Marten van Kerkwijk <
> m.h.vankerkwijk at gmail.com> wrote:
>
>>
>>
>> On Mon, Aug 27, 2018 at 10:05 PM Stephan Hoyer <shoyer at gmail.com> wrote:
>>
>> - It appears in astropy, dask, pandas, pint, scipy and TensorFlow.
>>>
>>
>> The only reason it appears in astropy is because of tests that Quantity
>> works correctly with it; we do not actually use it...
>>
>> So that's at least a few hits that do not count as arguments to keep it!
>> I'm in favour of a PendingDeprecationWarning.
>>
>
> We should at least first merge the PR that adds the same padding behavior
> to np.diff before doing this, then such a warning could say to just use
> that and get unchanged behavior.
>

The proposed behavior for np.diff() is different, but it should solve the
same use-cases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180828/cf319f3c/attachment.html>


More information about the NumPy-Discussion mailing list