Closed michaeltryby closed 5 years ago
Personally, I would prefer not having to mess around with Visual Studio 10 2010 any longer. There have been a lot of nice changes in C++11 that it lacks that make writing the unit tests painful. That means minimum supported version would be Python 3.5. And I guess that we are stuck supporting 32-bit until the engine has been ported.
Need to investigate how to build a Python 3 universal wheel like WNTR distributes.
This article on binary compatibility is also helpful. https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2015-2017?view=vs-2017
Python Windows Platform Compilers: Python 2.7 - Visual Studio 9 2008 Python 3.3, 3.4 - Visual Studio 10 2010 Python 3.5, 3.6, 3.7 - Visual Studio 14 2015
Current EPANET benchmark builds on Visual Studio 15 2017
PyQGIS targets Python 3.6 Should we support Python 2.7, 3.3, 3.4?