Neil Girdhar

@njsmith Could we start with the deprecation? At least in the docs?

@njsmith I understand. Thanks for explaining. It might be a good idea to at least have easy ways to write that code that does not rely on the weird `==`....

@njsmith Ah, of course. Right, so that's probably the first step. I don't understand why is `np.float is float` and not `np.float64`? When I do `np.zeros(10, dtype=np.float).dtype` I get `np.float64`....

@rkern Wow, yeah that's really unfortunate.

@rkern Also I don't think that Python promises that `float` will be 64 bits. I thought it was a CPython design decision?

Would it be possible to repair this comparison in `numpy.array_api`? That is, make `np.array_api.bool != 'bool' != np.array_api.bool.type`? And perhaps also edit the Array API standard to make this invariant...

> I got a little lazy and decided not to wrap the dtype objects in numpy.array_api Right, I understand the simplicity there, but unfortunately that means that the Array API...

> It's still a broken hash so we're preserving a bug. How is removing hashability better than simply making them hash differently as proposed in the issue? Also, `dict[DType, float]`,...

I like that idea! What do you think of reorganizing the "element-wise functions" in [the Array API's index](https://data-apis.org/array-api/latest/API_specification/index.html#) to match NumPy's index? I think NumPy's organization is more logical and...

Does this look okay? @yashk2810