Sebastian Berg
Sebastian Berg
Those are all pretty harmless warnings even if they indicated broken ABI use related to long doubles, what else do you see? just a hard crash?
That is correct, inplace operators cannot and thus must not be implemented. `__complex__` makes a lot of sense to be missing, precisely because it is *not* an `nb_` slot, but...
Thanks @eendebakpt the change LGTM (unrelated return changes are also fine). I doubt it will make issues, but maybe add a very short release note anyway?
Arrg, I noticed one thing that _maybe_ we should defer. But our scalars do the same dance and still return the Python boolean. And while it is easy to change...
Ah, I guess only the ones for which the comparison is not defined `np.float64(3) != np.str_("a")`. I.e. this path, but for scalars.
OK, thanks @eendebakpt let's give this a try. FWIW, we should of course return a 0-D array in some future (which this does not make any harder, I suspect it...
Ufff, yes, that changed it, but the problem is that the `.fill_value` ends up being an `int64` rather than the `uint64` of the masked array. IIRC, that was a work-around...
> I think the default value should be reconsidered Yes, that is probably the right thing to do. I haven't caught up with your many posts (it is great to...
Closing as fixed in pandas.
That sounds nice, I think it makes sense to build with `numpy~=2.0` (which tends to give us the newest possible). That way we can ship header fixes. Even better, I...