You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we could release the cucim.skimage portion of the package (e.g., cucim_cu12-24.8.0-py3-none-win_amd64.whl) in the PyPI registry without including the unnecessary/non-supported IO portion (shared libraries) of cuCIM.
I believe there is a straightforward way to build and register a Windows Python wheel by updating cucim/ci/build_wheel.sh at branch-24.10 · rapidsai/cucim and register to Windows PyPI package along with the original wheel file (executing this only for a specific build configuration).
# The following will create cucim_cu12-24.6.0-py3-none-win_amd64.whl file.
wheel tags --python-tag=py3 --abi-tag=none --platform-tag=win_amd64 cucim_cu12-24.6.0-cp311-cp311-manylinux_2_28_aarch64.whl
The text was updated successfully, but these errors were encountered:
We discussed this in the cuCIM meeting today after feedback from RAPIDS OPS. Based on this we revised our plan, which is sketched below
This would split out the Python/C++ bits into pylibcucim and the pure Python bits into pycucim. The cucim package would become a meta package that pulls both in where supported. If the pylibcucim is not supported on a platform (like Windows currently), we would select it out. So users would still install cucim. It would just now work on other platforms not supported today (like Windows) by pulling in the pure Python bits only
Is your feature request related to a problem? Please describe.
There is an increasing number of requests from users who want to use the
cucim.skimage
module (which depends on CuPy) on other platforms (non-Linux).python/skimage
to aconda
channel (orpypi
) #748It would be great if we could release the
cucim.skimage
portion of the package (e.g., cucim_cu12-24.8.0-py3-none-win_amd64.whl) in the PyPI registry without including the unnecessary/non-supported IO portion (shared libraries) of cuCIM.Describe the solution you'd like
I believe there is a straightforward way to build and register a Windows Python wheel by updating cucim/ci/build_wheel.sh at branch-24.10 · rapidsai/cucim and register to Windows PyPI package along with the original wheel file (executing this only for a specific build configuration).
# The following will create cucim_cu12-24.6.0-py3-none-win_amd64.whl file. wheel tags --python-tag=py3 --abi-tag=none --platform-tag=win_amd64 cucim_cu12-24.6.0-cp311-cp311-manylinux_2_28_aarch64.whl
The text was updated successfully, but these errors were encountered: