From 4e18344028d1bb6236640690f690edb1eba1c8f1 Mon Sep 17 00:00:00 2001 From: Changming Sun Date: Fri, 31 May 2024 14:01:11 -0700 Subject: [PATCH] Delete docs/Python_Dev_Notes.md (#20887) It is no longer relevant since it is not a problem since python 3.5, and the minimum python version we support is 3.8. --- docs/Python_Dev_Notes.md | 18 ------------------ 1 file changed, 18 deletions(-) delete mode 100644 docs/Python_Dev_Notes.md diff --git a/docs/Python_Dev_Notes.md b/docs/Python_Dev_Notes.md deleted file mode 100644 index 78804bd9f2f86..0000000000000 --- a/docs/Python_Dev_Notes.md +++ /dev/null @@ -1,18 +0,0 @@ -# Python Dev Notes - -Each Python version uses a specific compiler version. In most cases, you should use the same compiler version for building python extensions. - -## Which Microsoft Visual C++ compiler to use with a specific Python version ? - -| Visual C++ | CPython | -|-------------|:-----------------------:| -|2015, 2017 | 3.7 | -|2015 | 3.5,3.6 | -|2010 | 3.3,3.4 | -|2008 | 2.6, 2.7, 3.0, 3.1, 3.2 | - -Currently, the official ONNXRuntime Python wheel (v1.3.0 onwards) hosted on PyPi requires [Visual C++ 2019 runtime ](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads) installed on the target machine. - -If the Python wheel is built from source using the build toolset provided with Visual Studio 2017, it will work with the Visual C++ 2017 runtime. - -CPython 3.7 is distributed with a VC++ 2017 runtime. Unlike the earlier VC++ version, VC++ 2017 Runtime is binary backward compatible with VC++ 2015. Which means you could build your application with VC++ 2015 then run it with VC++ 2017 runtime.