Mateusz Sokół

@conda-forge/help-python @conda-forge/help-c-cpp It's ready for a review!

@traversaro let's just wait for the CI to turn green. I noticed that linux failed with internal bazel issue, probably caused by something that bazel cached.

@traversaro Thank you for pointing it out - I wasn't aware of that toolchain. I've got linux build working now (had the same [bazel issue here](https://github.com/prefix-dev/rattler-build/issues/1865) as jax feedstock). The...

> This is pure C++ code, whose only dependency is pybind11, so it should only required 2 invocation of the compiler for each Python version, so more and less ~10...

> For example, perhaps we can run `bazel build //grain/_src/python/experimental/index_shuffle/python:index_shuffle_module` instead of `bazel build ...` to only build what we actually need? @traversaro Unfortunately we can't narrow the build to...

> As long as the releases are not so often It looks like Grain has been being released [once a month so far](https://pypi.org/project/grain/#history) and it shouldn't increase IMO. The argument...

> In that case, can you look into adding an appropriate upper bound for the `protobuf` version used at runtime? To avoid errors like https://github.com/grpc/grpc/issues/39912?utm_source=chatgpt.com . It may also make...

Thank you for writing a thorough comparison! ## Changes that are not detected at all I think that most of these members were niche, and GitHub search showed none or...

> np.issctype, np.maximum_sctype, np.obj2sctype, np.sctype2char, np.sctypes were all removed from the main namespace without replacement, as they where niche members. I think ruff Rule detects all of them.

Will be partially fixed in https://github.com/astral-sh/ruff/pull/12065.