Closed hmaarrfk closed 6 months ago
Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe
) and found it was in an excellent condition.
Hmmm... Could you please just install cupy-core
in a CPU-only env?
Hmmm... Could you please just install cupy-core in a CPU-only env?
I'll try. I take it that import cupy
with full python namespace should exist in your opinion?
Yes that's right.
Yes that's right.
I anticipated that this would be the case. Might be a pretty big uphill battle, but I'll likely try periodically over the year.
Hey Mark, could you please help us understand what issues you are still encountering?
On my MacBook Pro M1 (no NVIDIA GPU), I was able to use one of our conda-forge containers, install cupy-core
, and import cupy
without issues. Please see details below:
Please see https://github.com/conda-forge/staged-recipes/pull/25925
I want, in order of priority:
Other packages, tensorflow, pytorch, have a "cpu-only" version that allows packages to "depend on them" without incurring the large downloads
Could you please share a bit more on why macOS is needed? AFAICT that hasn't been supported by CuPy in a while ( https://github.com/cupy/cupy/pull/3857 )
Otherwise it sounds like cupy-core
maps pretty closely to what you are looking for
The other consideration would be to use the Array API in the library, which both NumPy and CuPy support. That way the code can seamlessly work on CPU or GPU based on the array type provided
The concern is not for runtime, but for the packaging time.
Could you please share a bit more on why macOS is needed?
I would like to avoid having OSX and CUDA variants of my package.
Otherwise it sounds like cupy-core maps pretty closely to what you are looking for
yes. close, but doesn't hit Point 1, nor 3.
The other consideration would be to use the Array API in the library
Maybe our cupy is a little rusty, we could not get around calls to array.get()
to get the results of the computation into CPU memory.
Could you please explain why cupy-core
doesn't meet 3? It doesn't pull in any CUDA libraries. They are optional and constrained
Sorry for my brief reply, I was on a ferry and could not expand further...
CuPy does not support macOS because neither CUDA nor ROCm (its two underlying accelerator backends) supports it. Note that CuPy does not even has a CPU backend; NumPy was meant to be used for that purpose. As John noted, CuPy's legacy macOS support has been long broken and I removed it, so you wouldn't even be able to build CuPy on macOS and I'd suggest to not waste time trying. If you think a skeleton package (which by my definition is importable but not functional) for macOS is absolutely needed, please open an issue in CuPy to discuss. But other than this, I think cupy-core
, offered starting CuPy v13, should meet the rest of your needs exactly.
Software support isn't needed. Mostly just "ease of optionally depending on my environment and recipes "
I'll likely make my own special package outside of conda forge for this and see what learnings I can share.
The goal would be to avoid CPUs users having to download a 700 MB download if they add this as a dependency. Checklist
0
(if the version changed)conda-smithy
(Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)