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

	Commit message (Collapse)	Author	Age	Files	Lines
*	gh-81057: Get the c-analyzer tool working again. (gh-92246)	Eric Snow	2022-05-03	1	-2/+5
\|
*	bpo-47152: Move sources of the _sre module into a subdirectory (GH-32290)	Serhiy Storchaka	2022-04-04	1	-3/+3
\|
*	bpo-36876: Make sure the c-analyzer is checking all the source files.' ↵	Eric Snow	2022-02-10	1	-1/+7
\| \| \| \| \|	(gh-31264) https://bugs.python.org/issue36876
*	bpo-45952: Get the C analyzer tool working again. (gh-31220)	Eric Snow	2022-02-08	1	-0/+1
\| \| \|	https://bugs.python.org/issue45952
*	bpo-45952: Get the C analyzer tool working again. (gh-31219)	Eric Snow	2022-02-08	1	-0/+3
\| \| \|	https://bugs.python.org/issue45952
*	bpo-45952: Get the C analyzer tool working again. (gh-29882)	Eric Snow	2021-12-01	1	-26/+55
\| \| \| \| \|	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
*	bpo-35081: Move interpreteridobject.h to Include/internal/ (GH-28969)	Victor Stinner	2021-10-15	1	-1/+0
\| \| \| \|	Move the interpreteridobject.h header file from Include/ to Include/internal/. It only provides private functions.
*	bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵	Eric Snow	2020-12-24	1	-35/+1
\| \| \| \| \| \| \|	(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	-0/+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/+43
\| \| \|	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	-0/+308
	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