Supporting non-standard CPython VC builds on Windows

The current system of having the version Windows’ MSVC tied to the CPython is troublesome for people in some cases. In particular, with respect to cases where people needed the latest compiler features (e.g. C++11 features). There may be other relevant cases, as well. The main purpose of this issue is to suggest that we include some (maybe even just one) compilation of a non-standard CPython VC build on Windows to simplify things for the conda community. Of course, making this change could disrupt the current feature landscape of Windows CPython so needs some thought on that point. This issue is also opened to get feedback from the conda community to determine which non-standard CPython VC builds would be valuable and thus be worthwhile to support. At present, I am thinking a vc14 (i.e. Visual Studio 2015) variant of CPython 2.7.x (where x will always be latest) is almost certainly worthwhile just to get C++11 support. Though am not sure if there are other worthwhile non-standard variants to consider.

cc @ukoethe @jasongrout @SylvainCorlay @msarahan @mcg1969

[jakirkham]

Well, it looks like the conclusion to be drawn from this is best summarized in this post by the aforementioned Microsoft developer. Basically, the breakage would be too bad to consider using other VCs either for CPython 2.7 or extensions and that it should be prohibited. The remainder of the threader tapers off into stuff that we are not concerned with here before ending.

So, maybe the answer here is it would be technically unfeasible to approach this topic, unfortunately. Sorry to get people’s hopes up here, but I don’t think we are any better equipped to solve this problem. I am going to close this issue as won’t fix. Though people are welcome to discuss further.

[pelson]

A healthy debate, and well conducted on all fronts. Thanks to everybody for keeping focussed on the issue and putting time & effort on making your points of view clear and succinct. 👍