Paule Moore, a new Python contributor, is prepared to help significantly as I understand it, but he deems support for the new CRT somewhat of a requirement to get streamlined support for the GCC/Windows/Python combination. > Now, it seems that VS2015 is coming with a new 'Universal CRT', which will be what the new Python version supports. For that issue, and the flicker of activity, see this bug report: The biggest issue being that you cannot simply build Python extensions with MinGW(-w64). > For a long time, GCC on Windows was not a usable option for Python without some pretty big workarounds and hacks to get everything working. > There has recently (as in, yesterday) been a new flicker of activity in the mingw-python camp. As to that, is thereĪny (significant/important) difference between the MSYS2 builds and the Python patches located here which can be used as a starting point:Īdditionally, there seem to be some misconceptions as to the number ofĭifferent toolchains available, I'll offer to straighten that out with him,Īnd point him to the official builds we offer here. This being added to MinGW-w64 'soon'? I'll be sure to point him to the Support for the GCC/Windows/Python combination. Paule Moore, a new PythonĬontributor, is prepared to help significantly as I understand it, but heĭeems support for the new CRT somewhat of a requirement to get streamlined

Now, it seems that VS2015 is coming with a new 'Universal CRT', which willīe what the new Python version supports. For that issue, and the flicker of activity, see this bug Theīiggest issue being that you cannot simply build Python extensions with Some pretty big workarounds and hacks to get everything working. There has recently (as in, yesterday) been a new flicker of activity in theįor a long time, GCC on Windows was not a usable option for Python without

Universal crt windows 10