Yes, that is the change I am thinking of. And yes, it hasn't happened yet.
But, it has been set to warn for a few years now, and there was a lot of
controversy over it when it was first proposed. That said, I do think the
way it was handled made sense, and it is a good model to follow for these
typ
On 07/18/2017 09:52 AM, Benjamin Root wrote:
> This sort of change seems very similar to the np.diag() change a few years
> ago. Are there lessons we could learn from then that we could apply to here?
>
> Why would the returned view not be a masked array?
>
> Ben Root
I am in favor of the propos
This sort of change seems very similar to the np.diag() change a few years
ago. Are there lessons we could learn from then that we could apply to here?
Why would the returned view not be a masked array?
Ben Root
On Tue, Jul 18, 2017 at 9:37 AM, Eric Wieser
wrote:
> When using ndarray.squeeze,
When using ndarray.squeeze, a view is returned, which means you can do the
follow (somewhat-contrived) operation:
>>> def fill_contrived(a):
a.squeeze()[...] = 2
return a
>>> fill_contrived(np.array([1]))
array(2)
However, when tried with a masked array, this can fail, breaking li
