cpython.git - https://github.com/python/cpython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	gh-105407: Remove unused imports in Tools/c-analyzer/ (#105410)	Victor Stinner	2023-06-06	1	-1/+0
\|
*	gh-102033: Fix syntax error in `Tools/c-analyzer` (GH-102066)	Nikita Sobolev	2023-03-22	3	-4/+0
\| \| \|	The easiest way to format strings with `{}` meaningful chars is via `%`.
*	gh-90110: Fix the c-analyzer Tool (gh-96731)	Eric Snow	2022-09-12	1	-0/+19
\| \| \| \| \| \| \|	This includes: * update the whitelists * fixes so we can stop ignoring some of the files * ensure Include/cpython/*.h get analyzed
*	gh-94673: [c-analyzer] Add a Script to Identify Static Types (#94989)	Eric Snow	2022-07-19	1	-122/+163
\| \| \|	issue: https://github.com/python/cpython/issues/94673
*	Fix typos in the Tools directory (GH-28769)	Christian Clauss	2021-10-06	2	-2/+2
\| \| \| \| \| \| \|	Like #28744 but for the Tools directory. [skip issue] Opening a related issue is pending python/psf-infra-meta#130 Automerge-Triggered-By: GH:pablogsal
*	bpo-44786: Fix a warning in RE in c-analyzer (GH-28351)	Serhiy Storchaka	2021-09-15	1	-2/+2
\|
*	bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵	Eric Snow	2020-12-24	2	-12/+188
\| \| \| \| \| \| \|	(gh-23918) This will help identify which C-API items will need to be updated for subinterpreter support. https://bugs.python.org/issue36876
*	bpo-36876: [c-analyzer tool] Tighten up the results and output. (GH-23431)	Eric Snow	2020-11-20	3	-45/+122
\| \| \|	We also update the "ignored" file with a temporary list of all known globals.
*	bpo-36876: Small adjustments to the C-analyzer tool. (GH-23045)	Eric Snow	2020-10-30	1	-3/+48
\| \| \|	This is a little bit of clean-up, small fixes, and additional helpers prior to building an updated & accurate list of globals to eliminate.
*	bpo-36876: Fix the C analyzer tool. (GH-22841)	Eric Snow	2020-10-23	11	-0/+1457
	The original tool wasn't working right and it was simpler to create a new one, partially re-using some of the old code. At this point the tool runs properly on the master. (Try: ./python Tools/c-analyzer/c-analyzer.py analyze.) It take ~40 seconds on my machine to analyze the full CPython code base. Note that we'll need to iron out some OS-specific stuff (e.g. preprocessor). We're okay though since this tool isn't used yet in our workflow. We will also need to verify the analysis results in detail before activating the check in CI, though I'm pretty sure it's close. https://bugs.python.org/issue36876