-
Notifications
You must be signed in to change notification settings - Fork 45
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
[QST] Implement consistent usage of rapids_cmake_support_conda_env #334
Comments
You mean the python side of cudf correct ? since |
You're right that libcudf uses it, although it does so a bit differently since both cuml and raft both support configuring whether it's called using the And then yes, figuring out what if anything we should be doing on the Python side. |
I agree on standardization behavior around conda env detection and behavior. On that front I am not a fan of the behavior the some projects have where they change the |
What is your question?
This isn't strictly a question about rapids-cmake so much as a question about its usage across RAPIDS, but there isn't a great place to raise this question so sticking it here for now. Right now it looks like only cuML and raft use this functionality, but I assume we want to handle it consistently in all packages.
The text was updated successfully, but these errors were encountered: