Skip to content

DOC: Add admonition to docstrings for cuda.core handle properties #573

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

Merged
merged 3 commits into from
Apr 26, 2025

Conversation

carterbox
Copy link
Contributor

Description

Adds caution admonition to documentation for users who are accessing the handle property of cuda.core objects. The alternative was to add a docstring for int() for the cuda.bindings python objects. However, these python objects are autogenerated, and I couldn't see where the bindings were generated from. There's just text at the top of all the pyx files that state the bindings are autogenerated and that they should not be manually edited.

closes #557

Checklist

  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

Copy link
Contributor

copy-pr-bot bot commented Apr 22, 2025

Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@carterbox carterbox force-pushed the dching/note-CUObject-c-pointer branch from 3ccaf67 to 70ff96b Compare April 22, 2025 23:26
@carterbox
Copy link
Contributor Author

/ok to test 70ff96b

@leofang leofang self-requested a review April 22, 2025 23:30
@leofang leofang added documentation Improvements or additions to documentation P1 Medium priority - Should do cuda.core Everything related to the cuda.core module labels Apr 22, 2025
@leofang leofang added this to the cuda.core beta 4 milestone Apr 22, 2025

This comment has been minimized.

@leofang
Copy link
Member

leofang commented Apr 25, 2025

Sorry for delay @carterbox. Would you mind making the following changes:

  • python -> Python (capitalized)
  • the C struct -> the underlying C handle (most objects we're dealing with are just typed pointers/opaque descriptors)
  • do not mention getPtr

@carterbox
Copy link
Contributor Author

/ok to test 8d87136

Copy link
Member

@leofang leofang left a comment

Choose a reason for hiding this comment

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

Another nit: Could you please not @ me in the commit message? GitHub messes up handling that, and I often ended up receiving dozens of notifications...

@carterbox carterbox force-pushed the dching/note-CUObject-c-pointer branch from 8d87136 to db2d0b4 Compare April 25, 2025 20:43
@carterbox
Copy link
Contributor Author

/ok to test db2d0b4

@carterbox carterbox requested a review from leofang April 25, 2025 21:41
@leofang leofang merged commit c71ed39 into NVIDIA:main Apr 26, 2025
75 checks passed
@leofang
Copy link
Member

leofang commented Apr 26, 2025

Thank you, Daniel!

Copy link

Doc Preview CI
Preview removed because the pull request was closed or merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuda.core Everything related to the cuda.core module documentation Improvements or additions to documentation P1 Medium priority - Should do
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Correct usage of cuda.core._memory.Buffer?
2 participants