find-cpython-usage

CPython internal headers like internal/pycore* and Python.h are located by scanning source files with grep. Search across .c, .cpp, .h, .hpp, and .pyx files to capture all includes, then document findings in a reference file for version compatibility validation.

Common CPython structs include frame, code, and thread state objects. Document where these structs are accessed in your codebase and which fields are directly used, then map findings to source files to enable version comparison across Python releases.

CPython internal APIs change between versions, affecting profilers and native extensions. Identifying which internal headers and structs your code relies on reveals compatibility risks and guides targeted testing when upgrading to new Python versions.

Yes. Scan native extensions for internal header includes and struct accesses, document the results, and use that reference to validate compatibility with the target Python version before deploying the upgrade.

Compile a findings file listing all included CPython headers, accessed structs, and directly used fields mapped to their source files. This centralized reference enables systematic compatibility validation and simplifies handoff to version comparison workflows.