Steve Dower added the comment:
CMD is not going to be subjected to compatibility shims that hide the version
number, and I *think* those are not inherited by child processes. So it can use
the basic APIs. (It's also likely to be the comparison that most people will
check against.)
I agree t
Eryk Sun added the comment:
> For the other 10% (diagnostic logging), it would be nice to have a
> better option than running "cmd /c ver"
CMD's VER command (cmd!eVersion) calls GetVersion(), for which, in its case,
the API calls the internal function GetVersion_Current(). The VER command als
Steve Dower added the comment:
Yeah, that all makes sense. 90%+ of the time, checking the version number is a
compatibility issue waiting to happen.
For the other 10% (diagnostic logging), it would be nice to have a better
option than running "cmd /c ver", but that might be the easiest thing
Eryk Sun added the comment:
Note that the following recommendation for getting the system version was
removed in late 2019 [1][2]:
To obtain the full version number for the operating system,
call the GetFileVersionInfo function on one of the system
DLLs, such as Kernel32.dll, then
Steve Dower added the comment:
Nothing has changed in platform, and all current releases return the same
version number for me (which matches the original report).
As I said, we need to find a versioned DLL that _always_ rebuilds to extract
the version number from, because that's the most re
OrbitalHorizons added the comment:
Platform seems to have been fixed as all pre release builds were fetched as
intended shortly after the post was created here, however Windows 10 Version
10.0.19042 is still unable to be displayed by the Python platform module in my
Python 3.8.8 system.
---
