➜

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 lemburg
Recipients brian.curtin, giampaolo.rodola, jkloth, lemburg, loewis, pitrou, serhiy.storchaka, steve.dower, tim.golden, tim.peters, zach.ware
Date 2014-06-10.11:15:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402398938.7.0.0469292278011.issue19143@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't have a Windows 8.1 handy, but if "ver" reports the correct version, why not have platform.win32_ver() use _syscmd_ver() in case the other APIs report "6.2.9200" and then have win32_ver() the higher version ?!

FWIW: I don't think we should add anything to the python.exe manifest to have it report the correct version. This could potentially break other APIs. AFAIK, MS just used this "trick" to prevent having existing 8.0 applications fail on 8.1 due to the minor version bump. I suppose they'll undo this with the next official Windows release.
History
Date User Action Args
2014-06-10 11:15:38lemburgsetrecipients: + lemburg, tim.peters, loewis, pitrou, giampaolo.rodola, tim.golden, jkloth, brian.curtin, zach.ware, serhiy.storchaka, steve.dower
2014-06-10 11:15:38lemburgsetmessageid: <1402398938.7.0.0469292278011.issue19143@psf.upfronthosting.co.za>
2014-06-10 11:15:38lemburglinkissue19143 messages
2014-06-10 11:15:38lemburgcreate