In many other parts of numpy, calling the numpy function that had an
equivalent array method would result in the method being called. I would
certainly be surprised if the copy() method behaved differently from the
np.copy() function.
Now it is time for me to do some grepping of my code-bases...
On Mon, Oct 19, 2015 at 8:28 PM, Nathan Goldbaum
wrote:
>
>
> On Mon, Oct 19, 2015 at 7:23 PM, Jonathan Helmus
> wrote:
>
>> In GitHub issue #3474, a number of us have started a conversation on how
>> NumPy's copy function should behave when passed an instance which is a
>> sub-class of the arra
On Mon, Oct 19, 2015 at 7:23 PM, Jonathan Helmus wrote:
> In GitHub issue #3474, a number of us have started a conversation on how
> NumPy's copy function should behave when passed an instance which is a
> sub-class of the array class. Specifically, the issue began by noting that
> when a Masked
In GitHub issue #3474, a number of us have started a conversation on how
NumPy's copy function should behave when passed an instance which is a
sub-class of the array class. Specifically, the issue began by noting
that when a MaskedArray is passed to np.copy, the sub-class is not
passed throug
