As per https://marc.info/?l=kde-core-devel&m=150464598710128&w=2, this is a snapshot of the current state of the SIP-based Python binding generator intended for KF5, KDE, and more generally.
Beyond what I mentioned in the post, the key differences compared to what is in ECM might be summarised as follows:
- The core logic has several sets of fragile heuristics replaced by more solid logic based on Clang structures. (The remaining heuristics cannot, as far as I can see from the internals of Clang, be done away with).
- There is an approach to portability built atop CMake, but intended to support operation as a standalone utility, as opposed to being integrated into ECM.