Sept. 25, 2015
3:24 p.m.
This is the main motivation for moving to VS 2015 for Python 3.5.
Yes,I've followed that work to the degree I understand it, and it looks like a great move. Thanks so much for your (continuing) efforts with this.
put a bit of
pressure on MS to make it available, as they have for VS2008 and py2.7, that would be great.
I've applied that pressure already and it's not going to happen :(
Darn. Makes no sense, but I work for almost as big a bureaucracy as MS, so I know how that goes... :-)
The best "solution" is to move to Py 3.5 asap.
Really not a solution at all, I'm afraid, and there are still growing pains with compiling for it as well (see Numpy/SciPy). But thanks. -Chris