On 4/11/20, Barry Scott <ba...@barrys-emacs.org> wrote: >> On 10 Apr 2020, at 20:14, Christopher Barker <python...@gmail.com> wrote: >> >> Also, if order to get python top level scripts to work, there needs to be >> a PATH entry for that, too. > > Do you mean the #! lines? That is taken care of by py.exe and how it was > installed.
I think by "top level" Christopher means running "foo.py" directly, or just "foo" if ".PY" is in PATHEXT. The installer's option to update environment variables adds the "Scripts" directory to PATH and adds the .PY and .PYW file extensions to PATHEXT. It would be more flexible to split this out as an independent option. (Note that the "Scripts" directory also contains scripts that are embedded in a launcher executable, such as pip.exe, which distlib uses for entry-point scripts. But many entry-point scripts are commonly run via py.exe instead, such as `py -m pip`.) _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/22OFVG52S522CDTRZXLTL4DEX26522RS/ Code of Conduct: http://python.org/psf/codeofconduct/
