[Python-Dev] Python launcher command line usage (Was: 3.2.1 encoding surprise)

[Paul Moore]

On 20 July 2011 03:21, Terry Reedy <tjreedy at udel.edu> wrote:
> Suppose for Windows there were one '.../python' directory wherever the user
> first asks it to be put and that all pythons, not just cpython, are
> installed in directories below that and that the small startup file is
> copied into or linked from the python directory. Then the one python
> directory could be put on the path and left there and never removed by any
> python de-installer (unless perhaps it check that there are no subdirs and
> *asks* the user.

Hmm. Suppose that directory was "C:\Program Files\Python Launcher" (or
"C:\Windows\system32" if you don't want to add an extra directory to
PATH). And suppose that instead of having a startup file per Python
installation you have a single file called py.exe. Then you have the
launcher!

Plus, the launcher has its own uninstaller, making it a "normal" part
of the Windows environment, rather than being a directory created by
something which doesn't get uninstalled.

Plus, the launcher has a means of dealing with the "generic" python,
python2 and python3 commands, which your proposal doesn't.

Plus, the launcher deals with existing versions of Python, which your
proposal doesn't (except by manual intervention).

But yes, the idea is sound, which is why it's so similar to what Vinay
did with the launcher IMO.

Paul.