➜

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.16:59:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618765165.6.0.200544303347.issue43284@roundup.psfhosted.org>
In-reply-to
Content 
But kernel32.dll (since it's of a different version) isn't accurate at all right? To find the accurate result we have to use the CurrentBuildNumber registry key. I think this key will not be removed so easily by Microsoft. This key have been in existence from NT 3.5 till today. I think it's the safest and reliable way to get the version number other than WMI query. I know the key can be removed in the future but if it that happens what about reimplementing the kernel32.dll then. We need a way to get the accurate version right?
History
Date User Action Args
2021-04-18 16:59:25shreyanavigyansetrecipients: + shreyanavigyan, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, corona10, bugale bugale, Orbital
2021-04-18 16:59:25shreyanavigyansetmessageid: <1618765165.6.0.200544303347.issue43284@roundup.psfhosted.org>
2021-04-18 16:59:25shreyanavigyanlinkissue43284 messages
2021-04-18 16:59:25shreyanavigyancreate