Skip to content
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

[REVIEW] Python redesign for libcudf++ #3254

Merged
merged 223 commits into from
Jan 7, 2020

Conversation

shwina
Copy link
Contributor

@shwina shwina commented Oct 30, 2019

See the "redesign document" here.

See the corresponding RMM PR rapidsai/rmm#163

  • Rewrite Buffer to use rmm.DeviceBuffer instead of rmm.device_array underneath
  • Move Column to Cython and enable it to talk to both legacy libcudf and new libcudf++
  • [ ] Add example of porting Python functionality to libcudf++

@shwina shwina added 2 - In Progress Currently a work in progress Python Affects Python cuDF API. Cython labels Oct 30, 2019
@shwina shwina changed the title Python redesign for libcudf++ [DRAFT] Python redesign for libcudf++ Oct 30, 2019

CUDA_HOME = os.environ.get("CUDA_HOME", False)
if not CUDA_HOME:
CUDA_HOME = os.path.dirname(os.path.dirname(shutil.which("cuda-gdb")))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible that the user doesn't have cuda-gdb on their path, so CUDA_HOME could still not be found at this point. Might want to check it again and if not found, raise an exception telling the user to set CUDA_HOME.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's also possible the user has set the CUDA_HOME environment variable to a path which doesn't exist. @shwina is this needed long term or is this just a temporary workaround similar to cub / libcudacxx below?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raydouglass any opposition to us tackling this in a follow up pr?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kkraus14 Nope, it's just a nice-to-have to error out early on in my opinion since the user will get a compile error later that should make it obvious the CUDA includes are missing.

Copy link
Member

@rjzamora rjzamora left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dask_cudf-specific changes LGTM - Thanks for the hard work on this @shwina !

Copy link
Member

@jakirkham jakirkham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for all of your hard work on this @shwina! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Ready to Merge Testing and reviews complete, ready to merge Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.