CPython, C standards, and IEEE 754
I don&#x27;t know why GCC-12 was in the picture, but I hope all of you can understand one thing: python&#x27;s source code must be compatible with GCC 6. And no so called &quot;Threading [Optional]&quot; features. It is all because CentOS is dead. CentOS has been sold to IBM. There is no CentOS 8 anymore. The free lunch is ended. And there wouldn&#x27;t be another OSS project to replace it.<p>Linux kernel developers want to use C11. CPython developers want to use C11. But does your compiler support it? If you were a C++ developer, would you request C++17&#x2F;C++20 also?<p>CPython must be aligned with the manylinux project. manylinux build every python minor release from source. Historically manylinux only use CentOS.  CentOS has devtoolset, which allows you use the latest GCC in an very old Linux release. Red hat has spent much time on it. Now you can&#x27;t get it for free because CentOS is dead. So the manylinux community is switching to Ubuntu. Ubuntu can only provide GCC 6 to them. If anycode in CPython is not compatible with GCC6, then manylinux will have to drop ubuntu too. And they don&#x27;t have any other alternative. As I said, for now Red Hat devtoolset is the only solution. When IBM discontinued the CentOS project, most people do not understand what it means to the OSS community.<p>(I work for Microsoft. It doesn&#x27;t stop me to love Linux.)