Gregory Lee

> For now I've switched to using WSL2 for cucim, but for a native install I personally feel it would be best for the project to publish eggs that don't...

> I don't know if this PR is still relevant (please see https://github.com/scikit-image/scikit-image/pull/4464). A subset of this was done elsewhere (the `bg_label` default was changed from -1 to 0). I...

Hi @Schefflera-Arboricola, it's great to see this making progress on the scikit-image side! I remember we started looking at it at EuroSciPy and had seen that there had been some...

I posted one question about whether the plan on the scikit-image side is to initially only mark a couple functions as dispatchable? https://github.com/scikit-image/scikit-image/pull/7520/files#r1956590515 Also, FYI @Schefflera-Arboricola , for this project...

> And if you want, you can use can_has to check the size and convert the NumPy array into a CuPy array but you should not, because can_has is meant...

| and I think @stefanv in a meeting said that we want that-- i.e. to have input and output arrays of the same array type Definitely agree with @stefanv that...

We do not currently have an aarch64 package on PyPI but can potentially add one in the future. There are aarch64 packages in the [rapidsai conda channel](https://anaconda.org/rapidsai/cucim/files). See the release...

Thanks @gigony, I downloaded the Python 3.10 artifacts from the link you provided and installed the `cucim_cu12-24.10.0a9-py3-none-win_amd64.whl` in a Python 3.10 environment on a Windows 11 system with an RTX...

I fixed the existing conflicts. There were quite a few due to a recent rename from "grey"->"gray" and some refactoring that avoided use of `apply_along_axis`. I did not try to...

That would be consistent, however `_legacy_deprecation` was introduced in `v1.5` and still mentions removal in `v1.7.x` specifically. If we change everything to `_legacy_deprecation` then would we list it as `v1.10`?