bpo-36876: Add a tool that identifies unsupported global C variables.#15877
bpo-36876: Add a tool that identifies unsupported global C variables.#15877ericsnowcurrently merged 118 commits into
Conversation
|
115 commits, 51 files changes, and wow, that's a huge PR. |
Sorry, something went wrong.
|
" bpo-36876: Make sure no new globals get added." So far, the C API don't provide any solution for function "static PyObject *local_global_var = ...;" :-) |
Sorry, something went wrong.
23e9d06 to
de1f50f
Compare
September 11, 2019 11:06
|
Yeah, it's a lot, but it's all under Tools/. :) Also, I've updated the title to be more clear. |
Sorry, something went wrong.
de1f50f to
569c57e
Compare
September 11, 2019 12:19
|
FYI, all the failures are strictly with patchcheck, which is complaining about whitespace in some files. I cannot reproduce that locally. |
Sorry, something went wrong.
|
@ericsnowcurrently: Please replace |
Sorry, something went wrong.
This PR does 2 things:
For now the test is marked as a known failure. I'll be working to fix all of unsupported globals, at which point I'll unmark the test.
Note that this PR adds code to
Tools/c-analyzeror adds new tests. The only existing code I touch is where I factor out an existing testing helper from tests for another tool.https://bugs.python.org/issue36876