| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | gh-90110: Get the C Analyzer Tool Working Again (gh-95545) | Eric Snow | 2022-08-01 | 1 | -2/+5 |
| | | |||||
| * | bpo-36876: [c-analyzer tool] Add a "capi" subcommand to the c-analyzer tool. ↵ | Eric Snow | 2020-12-24 | 1 | -0/+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: Fix the C analyzer tool. (GH-22841) | Eric Snow | 2020-10-23 | 1 | -439/+26 |
| | | | | | | | | 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-41043: Escape literal part of the path for glob(). (GH-20994) | Serhiy Storchaka | 2020-06-20 | 1 | -1/+3 |
| | | |||||
| * | bpo-36876: Add a tool that identifies unsupported global C variables. (#15877) | Eric Snow | 2019-09-11 | 1 | -0/+446 |
 |
index : cpython.git | |
| https://github.com/python/cpython.git |
| summaryrefslogtreecommitdiffstats |