On Wed, Jul 10, 2019 at 1:58 PM Brendan Barnwell brenbarn@brenbarn.net wrote:
On 2019-07-09 23:23, Alex Walters wrote:
I have made this suggestion in the past. The response then was that
there
is no metadata in the windows install that includes if the release is development or stable (that information is not stored in the registry).
I
was advised to adjust my configuration of the py.exe launcher to set a different default version.
I think that's a reasonable stance to take with development versions -
they
are intended for testing in specialist situations, so you can expect the users to take the extra steps to make sure using them doesn't blow up
their
world.
It still would be nice if the registry details of the install had a bool "stable" field that py.exe could poll. I can't imagine it adds a lot to
the
release process, or adds significant complexity to the launcher, and that negates the need to update the launcher regularly.
I agree that it seems the real problem here is the lack of a realway to determine if an available version is a real release or a prerelease/beta. Is it not possible to change that, so that it is possible for the launcher to quickly and easily determine the highest release version available?
That's the question people are trying to figure out.