bpo-44426: Use of 'complex' as a variable name confuses recent Sphinx; change to 'num' #26744
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sphinx 4.0.2 misidentifies the name 'complex' as a C keyword, and issues a warning as a result. Sphinx is wrong here:
complex
is not a keyword (it's a macro), andPy_complex _Py_c_neg(Py_complex complex);
is a valid C declaration (unlesscomplex.h
has been included). Nevertheless, it's not a great name. This PR changes it tonum
, which is already used elsewhere in the same file.https://bugs.python.org/issue44426