Sebastian Berg

Interestingly, the [here](https://data-apis.org/array-api/latest/API_specification/generated/signatures.sorting_functions.sort.html) "descending" is used. I am a bit uncertain about that choice, since it is at odds with Pythons `sorted` and `sort`. In general, we should probably solve...

Adding one more note, since it is easy to miss. Not only is just reverting not stable, there is also the problem of NaN sort order. To me it seems...

FWIW, https://github.com/numpy/numpy/pull/28516 will probably add the basic infrastructure to do this soon. That said it doesn't implement it and we include other fast sorting code that may not do the...

@AA-Turner do you have time to finish these PRs up? Or maybe we'll just close them and you can open one (or more) with it when done?

The problem is how we should handle objects that are integer like (are currently converted to integers), but are _not_ proper Python integers in light of (NEP 50)[https://numpy.org/neps/nep-0050-scalar-promotion.html]. On NumPy...

Going to close this. Happy to see a PR that adds the definition to silence the warning though. (There is no change needed beyond defining the fact that cython 3...

We can probably change this, although I don't like that our scalars are mutable this way; it also doesn't really make much sense to act differently in different places. (I...

If the user has tight control of streams, they could just pass in the producer stream (meaning it is a no-op)? No real opion from me either way, but I...

That is correct, the old randomstate still uses `long` throughout, while the new one uses `int64`, so neither uses the "default integer" on NumPy 2. (although with the new rng...

It is already documented in the `dtype` argument (arguably, it affects the default as well of course): ``` .. warning:: This function defaults to the C-long dtype, which is 32bit...