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

	Commit message (Collapse)	Author	Age	Files	Lines
*	bpo-45952: Get the C analyzer tool working again. (gh-29882)	Eric Snow	2021-12-01	1	-1/+1
\| \| \| \| \|	There wasn't much that needed to be done. Mostly it was just a few new files that got added. https://bugs.python.org/issue45952
*	Fix typos in the Tools directory (GH-28769)	Christian Clauss	2021-10-06	1	-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-44854: Remove trailing whitespaces (GH-27689)	Serhiy Storchaka	2021-08-09	1	-1/+1
\|
*	bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵	Eric Snow	2020-12-24	1	-2/+3
\| \| \| \| \| \| \|	(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: Fix the C analyzer tool. (GH-22841)	Eric Snow	2020-10-23	6	-0/+815
	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