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

	Commit message (Collapse)	Author	Age	Files	Lines
*	gh-102033: Fix syntax error in `Tools/c-analyzer` (GH-102066)	Nikita Sobolev	2023-03-22	1	-2/+0
\| \| \|	The easiest way to format strings with `{}` meaningful chars is via `%`.
*	gh-81057: Add a CI Check for New Unsupported C Global Variables (gh-102506)	Eric Snow	2023-03-14	1	-8/+54
\| \| \| \| \| \| \| \| \| \| \|	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
*	gh-94673: [c-analyzer] Add a Script to Identify Static Types (#94989)	Eric Snow	2022-07-19	1	-1/+47
\| \| \|	issue: https://github.com/python/cpython/issues/94673
*	bpo-45952: Get the C analyzer tool working again. (gh-29882)	Eric Snow	2021-12-01	1	-0/+3
\| \| \| \| \|	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	-1/+1
\| \| \| \| \| \| \|	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-36876: [c-analyzer tool] Additional CLI updates for "capi" command. ↵	Eric Snow	2020-12-25	1	-5/+31
\| \| \| \| \|	(gh-23929) https://bugs.python.org/issue36876
*	bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵	Eric Snow	2020-12-24	1	-3/+101
\| \| \| \| \| \| \|	(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	1	-1/+6
\| \| \|	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	-1/+4
\| \| \|	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	1	-189/+257
\| \| \| \| \| \| \|	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
*	bpo-36876: Re-organize the c-analyzer tool code. (gh-16841)	Eric Snow	2019-10-19	1	-0/+212
	This is partly a cleanup of the code. It also is preparation for getting the variables from the source (cross-platform) rather than from the symbols. The change only touches the tool (and its tests).