ABI discussion is one thing. But if you into the discussion there is another - how to freeze the dependence … the more important question is transparency. It i

ABI discussion is one thing. But if you into the discussion there is another - how to freeze the dependence … the more important question is transparency. It is like docker sort of where you build up your final based on certain before image (binary c is the problem mentioned most). Can we have a way to document it all or even optional download all for the production software then freeze it. And testing document in a .sw_env_conf to keep the change vs the base. If it is a re-runnable and readable doc we can trace it. Sorry not solving the Abi but try to deal with the mess. Python is easy to learn and program. But running it is really. I document at least 7 Python version and control which one to use is itself hard.