Eric Snow 1ff81c0cb6 gh-81057: Add a CI Check for New Unsupported C Global Variables (gh-102506) ... This will keep us from adding new unsupported (i.e. non-const) C global variables, which would break interpreter isolation. FYI, historically it is very uncommon for new global variables to get added. Furthermore, it is rare for new code to break the c-analyzer. So the check should almost always pass unnoticed. Note that I've removed test_check_c_globals. A test wasn't a great fit conceptually and was super slow on debug builds. A CI check is a better fit. This also resolves gh-100237. https://github.com/python/cpython/issues/81057		2023-03-14 10:05:54 -06:00
..
parser	gh-90110: Fix the c-analyzer Tool (#102483)	2023-03-06 19:40:09 -07:00
preprocessor	gh-81057: Add a CI Check for New Unsupported C Global Variables (gh-102506)	2023-03-14 10:05:54 -06:00
__init__.py	gh-90110: Fix the c-analyzer Tool (gh-96731)	2022-09-12 11:09:31 -06:00
__main__.py	bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. (gh-23918)	2020-12-24 11:04:19 -07:00
_state_machine.py	gh-98401: Invalid escape sequences emits SyntaxWarning (#99011)	2022-11-03 17:53:25 +01:00
datafiles.py	bpo-36876: [c-analyzer tool] Tighten up the results and output. (GH-23431)	2020-11-20 15:39:28 -07:00
info.py	gh-90110: Update the c-analyzer Tool (gh-96255)	2022-08-25 15:46:08 -06:00
match.py	bpo-36876: Small adjustments to the C-analyzer tool. (GH-23045)	2020-10-30 15:46:52 -06:00
source.py	bpo-36876: Fix the C analyzer tool. (GH-22841)	2020-10-22 18:42:51 -06:00