-
Notifications
You must be signed in to change notification settings - Fork 159
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
DOC: Add admonition to docstrings for cuda.core handle properties #573
Conversation
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. |
3ccaf67
to
70ff96b
Compare
/ok to test 70ff96b |
This comment has been minimized.
This comment has been minimized.
Sorry for delay @carterbox. Would you mind making the following changes:
|
/ok to test 8d87136 |
There was a problem hiding this 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...
8d87136
to
db2d0b4
Compare
/ok to test db2d0b4 |
Thank you, Daniel! |
|
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