[BUG]: Failed to build from source due to unavailable rapids-dask-dependency
#4008
Comments
huiyuxie
added
? - Needs Triage
huiyuxie
changed the title
rapids-dask-dependencyrapids-dask-dependency
|
Hi @huiyuxie , I was able to reproduce your problem. The commands in the document you followed are not correct, so I've submitted this PR to update the doc. The issue is related to the new My recommendation is to simply run |
|
Thanks for the update @rlratzel ! |
closes #4008 * Removes unsupported `setup.py` calls, which resulted in issue #4008 . The document now describes how to use `build.sh`, which is more consistent with docs for other RAPIDS libs. * Removes `build.sh` output from docs in favor of documenting how to use `--help` to eliminate the doc being out-of-date with the script. * Removes extra wording in places and cleans up various sections. Authors: - Rick Ratzel (https://github.com/rlratzel) Approvers: - Don Acosta (https://github.com/acostadon) - Brad Rees (https://github.com/BradReesWork) URL: #4024
|
Thanks for bringing this to our attention. I just merged the PR to fix the docs, so I'll close this now. Please re-open or create another issue if there's still problems. |
Version
23.12
Which installation method(s) does this occur on?
Source
Describe the bug.
This issue is related to the recent commits #3991. Building from source worked well several days ago, but after these commits, the process failed. The errors came from the process here https://github.com/rapidsai/cugraph/blob/branch-23.12/docs/cugraph/source/installation/source_build.md#building-and-installing-the-python-package. The
pylibcugraphcould be installed without errors butcugraphpython bindings could not.The output showed that
error: Could not find suitable distribution for Requirement.parse('rapids-dask-dependency==23.12.*'). I think this might be because rapids-dask-dependency is a relatively new package that has not yet been published to PyPI. I'm not certain if this qualifies as a real bug, but since the issue is closely related to one, I've labeled it as a bug.Is it better to add this metapackage to dependencies later when its link becomes available on https://pypi.org/simple/, or is there another way to build from source, specifically during the installation process, to avoid these errors?
Minimum reproducible example
Relevant log output
Environment details
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: