Wouldn't doing an np.squeeze() on the result of ravel() do the trick? Not
sure about the implications with masked arrays and such, but just a thought.

That handles masked arrays well, but it still retains the shape (1, N) after the squeeze.

From the other thread, we need to make sure the docs are clear that mpl does not support matrix.

The correct way to fix this is probably to figure out each call site of np.asanyarray (there's like ~25 of them) to see whether they should be replaced by calls to np.asarray. The trick here is that you probably still want masked arrays to pass through, so perhaps you really need a helper function that behaves like asarray, except that masked arrays are passed through.

This helper function should probably(?) then be used in most places where either asarray or asanyarray is used.

Instead of only whitelisting masked arrays, it should blacklist matrix. Otherwise, you needlessly preclude other ndarray subclasses.

On 2016/10/11 9:17 AM, Ryan May wrote:

Instead of only whitelisting masked arrays, it should blacklist matrix.
Otherwise, you needlessly preclude other |ndarray| subclasses.

Right. The matrix subclass is an anomaly that causes more problems than
it is worth; it alters some of the most fundamental ndarray behavior.
In most discussions I have seen, the consensus advice is to discourage
its use.

Agreed, just blacklisting matrix and matrix subclasses seems better.