Author loewis
Recipients brian.curtin, jkloth, lemburg, loewis, pitrou, tim.golden, tim.peters
Date 2013-10-02.13:58:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380722323.08.0.859809276422.issue19143@psf.upfronthosting.co.za>
In-reply-to
Content
tim.peters: looking at the implementation of the proposed annoying functions with names like IsWindows8Point1OrGreater, it turns out that they all go back to VerifyVersionInfoW, which is available since W2k (but still doesn't tell the actual version).

tim.golden: a work-around is documented in 

http://msdn.microsoft.com/en-us/library/windows/desktop/dn302074.aspx

Put

<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>

into the manifest of python.exe, and it should report the correct version. Of course

a) this would fail for somebody embedding Python (unless they have that in their exe's manifest), and
b) we don't know the Id of upcoming windows versions, so the binaries produced today might still lie on future Windows releases.

It seems possible to query the compatibility using QueryActCtxW and CompatibilityInformationInActivationContext, but I couldn't find a way to put the compatibility into a new activation context (which would allow to claim compatibility dynamically).
History
Date User Action Args
2013-10-02 13:58:43loewissetrecipients: + loewis, lemburg, tim.peters, pitrou, tim.golden, jkloth, brian.curtin
2013-10-02 13:58:43loewissetmessageid: <1380722323.08.0.859809276422.issue19143@psf.upfronthosting.co.za>
2013-10-02 13:58:43loewislinkissue19143 messages
2013-10-02 13:58:42loewiscreate