[issue43284] Wrong windows build post version 2004

Steve Dower added the comment: The reason to avoid the GetVersion API is that certain automatic compatibility modes will lie about what the version number is, and people complained that it was wrong (kind of like this complaint ;) ). Reading the version from a system DLL bypasses that risk.

[issue43284] Wrong windows build post version 2004

OrbitalHorizons added the comment: Node Js version of os wasnt affected. If this is having an issue then they used some bootleg method to fetch the build number in the first place. -- ___ Python tracker

[issue43284] Wrong windows build post version 2004

bugale bugale added the comment: Is there a good reason to not use GetVersionEx? -- ___ Python tracker ___ ___ Python-bugs-list

[issue43284] Wrong windows build post version 2004

Steve Dower added the comment: So somehow Windows made a rebuild *without* having to touch kernel32.dll, which is fairly impressive. That version number comes from kernel32.dll, because there's no good way to get the build number via an API and also avoid compatibility settings lying about

[issue43284] Wrong windows build post version 2004

OrbitalHorizons added the comment: Running `platform.platform()` on Windows 10 21H1 results in the build number 19041: Python 3.8.8 (tags/v3.8.8:024d805, Feb 19 2021, 13:18:16) [MSC v.1928 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>>