I'm reading here you shouldn't mix MSVC versions as can result in hard to find side-effects.
Since Python 3.5 is compiled with MSVC2008 (v14.0) and Qt5 is available in a version compiled with MSVC2015 as well, we’re good to use that when compiling PySide2 for Python 3.5 using MSVC2015.
However, for Python 2.7 in Windows (which was compiled with MSVC2008 (v9.0) there's no Qt5 build, compiled with MVC2008. Right now I'm building Python 2.7 wheels for Windows using MSVC2015. I wonder if this is going to be OK...
I'm reading here you shouldn't mix MSVC versions as can result in hard to find side-effects.
Since Python 3.5 is compiled with MSVC2008 (v14.0) and Qt5 is available in a version compiled with MSVC2015 as well, we’re good to use that when compiling PySide2 for Python 3.5 using MSVC2015.
However, for Python 2.7 in Windows (which was compiled with MSVC2008 (v9.0) there's no Qt5 build, compiled with MVC2008. Right now I'm building Python 2.7 wheels for Windows using MSVC2015. I wonder if this is going to be OK...