-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-36381: warn when no PY_SSIZE_T_CLEAN #12473
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
Conversation
We will remove int support from 3.10 or 4.0.
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.
Thanks for your PR. IMHO it's time to deprecate that. Using int in 2019 can lead to bugs, most CPUs are 64-bit.
Doc/whatsnew/3.8.rst
Outdated
Changes in the C API | ||
-------------------- | ||
|
||
* Use of ``#`` variants of formats without ``PY_SSIZE_T_CLEAN`` defined |
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.
Hum, it's non obvious that these formats are used to parse function arguments. Maybe mention "ex: PyArg_ParseTuple"?
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.
I would add references to PyArg_ParseTuple and Py_BuildValue.
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.
Oh right, I always forget about Py_BuildValue() which is the "opposite" or PyArg_ParseTuple().
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.
LGTM, but the What's New entry should be more detailed.
Doc/whatsnew/3.8.rst
Outdated
Changes in the C API | ||
-------------------- | ||
|
||
* Use of ``#`` variants of formats without ``PY_SSIZE_T_CLEAN`` defined |
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.
I would add references to PyArg_ParseTuple and Py_BuildValue.
And replace PendingDeprecationWarning with DeprecationWarning.
The # variants the PyArg formats will raise deprecation warnings in py38. https://bugs.python.org/issue8677 https://bugs.python.org/issue36381 python/cpython#12473 python/cpython@d3c72a2
We will remove int support from 3.10 or 4.0.
https://bugs.python.org/issue8677