Issue #12 wontfix

Launcher prefers 3.3a1 over 3.2

Paul Moore
created an issue

When choosing the default version of Python (for the -3 flag, and presumably in general) the launcher picks up 3.3a1 in preference to 3.2. While this is arguably correct (use the latest version available) and can easily be fixed in py.ini it would be better if the launcher ignored non-released versions when choosing the default. The user can always explicitly request 3.3 should they want it.

Comments (2)

  1. Vinay Sajip

    Yes, but the present behaviour might also be desirable in some cases, with a user choosing a specific version (e.g. 3.2) if they want it.

    At the moment the launcher builds a list of Pythons by looking through the registry, and the question arises as to whether non-released versions should even be included in this list.

    There's also the question of what to do if -3 is specified and there's no other 3.x on the machine. Should an error be raised, or not (i.e. the non-released 3.x picked)?

    I'm not keen to complicate the selection logic over-much for something that might only affect us on the bleeding edge, so I'd like to see other opinions ;-)

  2. Log in to comment