@need a blank line between functions.

Yep, bad rebase...

(fixed)

For a little more efficiency, we could change this to:

nx.logical_and(nx.isinf(x, out), nx.signbit(x), out)

But that seemed out of scope for the bugfix/deprecation

Previous commit forgot to specify a stacklevel

The version of where you have above is not subclass-safe, at least not for Quantity (where, in general, the two arrays might have different units). For this particular function, it might nevertheless work, but I would suggest not introducing a new function. Instead, perhaps the following (I checked it passes all tests):

    out = nx.asanyarray(nx.floor(x, out=out))
    out = nx.ceil(x, out=out, where=(x < 0))
    return out if out.shape else out[()]

This should be out if type(out) != np.ndarray or out.shape else out[()], I think.

It should be whatever is closest to what a ufunc does; any subclasses should be able to deal with out[()]... (I guess the alternative would be to separate out the non-array case, but that seems overkill)

Yep, ufuncs only unpack scalars on the base classes, presumably as subclasses might lose metadata

Alright, fixed I think - it was a little bit messier than that

And one more time, with tests for the cases that your suggestion didn't cover