-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
PyTypeObject fields have incorrectly documented types #68996
Comments
Several fields in the Python 3.x documentation for the PyTypeObject API |
Most of this looks good. For the record, tp_flags was changed to unsigned in 3.4 (bpo-16086). The const and Py_ssize_t changes were done before 3.0. The only bits I would hesitate about are adding back the two comments saying “Assigned meaning in release 2”. These comments seem to have been removed from the Python 3 documentation in r67578, and I don’t see much point adding them back. I will have a go at committing the rest of the patch. (This is my first time making a commit.) |
New changeset 54a9c649281d by Martin Panter <vadmium> in branch '3.4': New changeset e81d692a00b1 by Martin Panter <vadmium> in branch '3.5': New changeset 2637e2593f01 by Martin Panter <vadmium> in branch 'default': |
Okay I think that worked smoothly (let me know if I missed something). Thanks for the patch Joseph. |
Congratulation on your first commit, Martin :) Dropping the python2 reference was the right call: the python3 docs are supposed to be a "fresh start" and there are very few places where they mention python2. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: