[issue21142] Daily/weekly ABI scan?

Batuhan added the comment: Tools/c-globals moved under Tools/c-analyzer -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-l

[issue21142] Daily/weekly ABI scan?

Eric Snow added the comment: That email thread contains multiple references to scripts that may be used to identify ABI issues, among other good points. FWIW, when consolidating the C globals last year I added a tool to track the remaining globals: Tools/c-globals It is similar (at least

[issue21142] Daily/weekly ABI scan?

Eric Snow added the comment: FTR, the issue of ABI breakage has come up quite a few times on the mailing list. Most recently: https://mail.python.org/pipermail/python-dev/2018-June/153775.html -- ___ Python tracker

[issue21142] Daily/weekly ABI scan?

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue21142] Daily/weekly ABI scan?

Nick Coghlan added the comment: Updated link to the ABI tracker report: https://abi-laboratory.pro/tracker/timeline/python/ (The stable ABI report still has a separate entry on http://upstream.rosalinux.ru/ but it links to the same report as I've linked above) I'm bumping this based on the

[issue21142] Daily/weekly ABI scan?

Andrey added the comment: There are just three simple steps to setup ABI checker: 1. Create ABI dump of the _reference_ version (see instructions [1]) and commit it to the source tree (ABI-ref.dump): $> abi-compliance-checker -l python -dump descriptor.xml -dump-path ABI-ref.dump 2. Create AB

[issue21142] Daily/weekly ABI scan?

New submission from Nick Coghlan: At Anatoly's prompting, Andrey Ponomarenko set up ABI/API compatibility checks for CPython on the Linux upstream tracker (http://upstream-tracker.org/) Everything: http://upstream-tracker.org/versions/python.html Public API/ABI (no leading underscores): http:/