On Fri, Nov 17, 2017 at 2:14 AM, Steve Barnes <gadgetsteve@live.co.uk> wrote:

>>> On Wed, Nov 15, 2017 at 11:07 AM, Steve Dower <steve.dower@python.org>
>>>> My preferred solution for this is to rename "py.exe" to "python.exe"


Note that renaming py.exe to python.exe would have several problems:


I don't understand any of this enough to have an opinion, so while I'd like to see py.exe be renamed python.exe, let's not let "the perfect be the enemy of good enough". So, if someone can make the case that they can restructure the whole py.exe / python.exe thing nicely in a way that will work, AND write the code to do it fairly quickly, then great!

Otherwise, let's at least get a python3.exe into 3.7 -- and ideally into updates to 3.5, 3.6, and (python2.exe in this case, 2.7)

And maybe make "add to PATH" be the default in the installer.

Those are quick and simple to do, result in little disruption, and make the whole cross-platform thing more manageable.

BTW -- does pip install a "pip3" on Windows?



Christopher Barker, Ph.D.

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception