-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch cupy-core
to allow it to be installed in CPU-only envs
#715
Conversation
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 ( |
@conda-forge/cupy this is ready Diff as generated by CI
|
You can also achieve this by a new build on the feedstock instead of a repodata patch. This would be preferred. |
Thanks, Uwe. Interesting because in the past I was advised to do the opposite (patch the repodata if possible so as to avoid unnecessary resource usage). Anyway I did also prepare a new build (conda-forge/cupy-feedstock#264), I will proceed there. |
The rule of thumb is that if it only affects a single feedstock and you can solve it by a new build, then do that. If there is a new release with e.g. a compatible ABI to the old version (i.e. ABI stability is better than run_exports), then patch the repodata over an (unnecessary) migration. |
xref: conda-forge/cupy-feedstock#264 (comment)
Checklist
generate_patch_json.py
if absolutely necessary.pre-commit run -a
and ensured all files pass the linting checks.python show_diff.py
and posted the output as part of the PR.