| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
Sorry, something went wrong.
|
@bedevere-bot (This issue seems too minor to warrant an issue number or a NEWS entry) |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for your contribution! cc @vstinner who worked on this file recently.
I think we can skip the news entry here because the problem it fixes hasn't been in any release (it's in the main branch only). If it had been in a release, we should have added a NEWS entry because it's a user-visible change.
I'll leave this open for a few days in case Victor or others have comments, and then merge.
Sorry, something went wrong.
|
(Commit amended with tweaked syntax) |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
Merged, thanks. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
When compiling my extension module against latest main version of CPython, I get many warnings related to unused parameters in unicodeobject.h. Example:
In file included from /Users/wjakob/nanobind/src/tensor.cpp:1: In file included from /Users/wjakob/nanobind/include/nanobind/tensor.h:14: In file included from /Users/wjakob/nanobind/include/nanobind/nanobind.h:37: In file included from /Users/wjakob/nanobind/include/nanobind/nb_python.h:22: In file included from /Users/wjakob/cpython-dist/include/python3.12/Python.h:51: In file included from /Users/wjakob/cpython-dist/include/python3.12/unicodeobject.h:1029: /Users/wjakob/cpython-dist/include/python3.12/cpython/unicodeobject.h:196:57: warning: unused parameter 'op' [-Wunused-parameter] static inline unsigned int PyUnicode_IS_READY(PyObject *op) { ^ /Users/wjakob/cpython-dist/include/python3.12/cpython/unicodeobject.h:416:45: warning: unused parameter 'op' [-Wunused-parameter] static inline int PyUnicode_READY(PyObject *op) ^This PR fixes those warnings. This isn't really a bug in Python, so I did not create a corresponding issue tracker ticket.