➜

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 shreyanavigyan
Recipients Orbital, bugale bugale, corona10, eryksun, paul.moore, shreyanavigyan, steve.dower, tim.golden, zach.ware
Date 2021-04-18.07:15:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618730152.57.0.0600639630685.issue43284@roundup.psfhosted.org>
In-reply-to
Content 
@eryksun described "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."

If that's the case why not get the version from CurrentBuild registry key present in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. This key at least goes back to Windows 7 and this is the key that's currently being used by winver command. And I don't think anyone at all uses windows version older than Windows 7. And chances are that the key maybe present even before Windows 7. At least the CurrentBuild is accurate.
History
Date User Action Args
2021-04-18 07:15:52shreyanavigyansetrecipients: + shreyanavigyan, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, corona10, bugale bugale, Orbital
2021-04-18 07:15:52shreyanavigyansetmessageid: <1618730152.57.0.0600639630685.issue43284@roundup.psfhosted.org>
2021-04-18 07:15:52shreyanavigyanlinkissue43284 messages
2021-04-18 07:15:52shreyanavigyancreate