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.12:19:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618748356.68.0.918723176635.issue43284@roundup.psfhosted.org>
In-reply-to
Content
I researched a little more and found that before Vista the winver command used the CurrentBuildNumber key instead of CurrentBuild key. In fact before Vista CurrentBuild was marked as obsolete by Microsoft. But that changed in Vista, when Microsoft started using CurrentBuild key instead of the CurrentBuildNumber key. Though still today CurrentBuildNumber key actually gives the exact version (for backward compatibilities maybe?). Therefore why not use CurrentBuildNumber? At least CurrentBuildNumber gives the right info. The only problem is that we have to only use that key to determine the windows version (Eg - Windows 10, 8.1, 8, 7, Vista, etc.) and to do that we have to use a very long switch or if-else statement. 

https://en.wikipedia.org/wiki/Comparison_of_Microsoft_Windows_versions#Windows_NT has the whole list with the column "RTM build" as the CurrentBuildNumber value.
History
Date User Action Args
2021-04-18 12:19:16shreyanavigyansetrecipients: + shreyanavigyan, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, corona10, bugale bugale, Orbital
2021-04-18 12:19:16shreyanavigyansetmessageid: <1618748356.68.0.918723176635.issue43284@roundup.psfhosted.org>
2021-04-18 12:19:16shreyanavigyanlinkissue43284 messages
2021-04-18 12:19:16shreyanavigyancreate