-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
The documentation for ctypes may be ambiguous. #116851
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
Comments
Shall we follow the advice in the FAQ and replace the other |
Sounds like a good idea. The whole doc seem inconsistent with |
@jnchen Thanks for the issue and PR, you make a good point |
…6852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import.
…ythonGH-116852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import. (cherry picked from commit 744c077) Co-authored-by: jnchen <[email protected]>
…ythonGH-116852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import. (cherry picked from commit 744c077) Co-authored-by: jnchen <[email protected]>
…GH-116852) (GH-116905) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import. (cherry picked from commit 744c077) Co-authored-by: jnchen <[email protected]>
…GH-116852) (GH-116906) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import. (cherry picked from commit 744c077) Co-authored-by: jnchen <[email protected]>
…ythonGH-116852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import.
…ythonGH-116852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import.
…ythonGH-116852) It is confusing, because libc is not imported from ctypes, but defined in previous examples, which already contain the import.
Uh oh!
There was an error while loading. Please reload this page.
Documentation
In this picture, after "from ctypes import *" then use the "libc.printf" may misleading the reader that libc from ctypes.
i think should remove "from ctypes import *" then tell reader this snippet continue with the above code
Linked PRs
The text was updated successfully, but these errors were encountered: