➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients Orbital, bugale bugale, corona10, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2021-03-16.18:56:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1615920972.41.0.518435560569.issue43284@roundup.psfhosted.org>
In-reply-to
Content 
Note that the following recommendation for getting the system version was removed in late 2019 [1][2]:

    To obtain the full version number for the operating system,
    call the GetFileVersionInfo function on one of the system
    DLLs, such as Kernel32.dll, then call VerQueryValue to obtain
    the \\StringFileInfo\\\\ProductVersion subblock of the file 
    version information.

The first commit added advice to check the "CurrentBuildNumber" registry value in Windows 10 1909+, but an engineer decided to just remove the paragraph. Apparently the developers do not want to guarantee that the version information on any particular system DLL can be used to get the system version. Apparently they also do not want to officially sanction using the "CurrentMajorVersionNumber", "CurrentMinorVersionNumber", and  "CurrentBuildNumber" values in the registry.

---

[1] https://github.com/MicrosoftDocs/win32/pull/143
[2] https://docs.microsoft.com/en-us/windows/win32/sysinfo/getting-the-system-version
History
Date User Action Args
2021-03-16 18:56:12eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, corona10, bugale bugale, Orbital
2021-03-16 18:56:12eryksunsetmessageid: <1615920972.41.0.518435560569.issue43284@roundup.psfhosted.org>
2021-03-16 18:56:12eryksunlinkissue43284 messages
2021-03-16 18:56:11eryksuncreate