RetroSearch Browse

Fri Feb 13 11:15:51 CET 2015 · http://mail.python.org/pipermail/python-dev/2015-February/138210.html

On 2/13/2015 1:13 AM, Paul Moore wrote:
> On 13 February 2015 at 06:59, Thomas Heller <theller at ctypes.org> wrote:
>> To make it clear: My suggestion is (or was, maybe it isn't a good idea)
>> to have some way to start 'something' that is in the Scripts
>> directory of a Python installation (which is usually a python script
>> or an exe-wrapper for it), without typing in the full path.  And without
>> changing the PATH envrionment variable.
> People using the old-style "scripts" keyword to setup() can put pretty
> much anything into the Scripts directory - I've seen .py files, Python
> files with no suffix, bat files, even Unix shell files (not much use
> on Windows...) in there. I don't think it's reasonable for the
> launcher to try to run all of those things.
>
> Maybe restricting it to running ".py" files or ".exe" files would be
> reasonable. That covers entry points (which should be the norm for
> newer projects) and Python scripts (which are the most likely things
> to be portable).
The WINDOWS py launcher hardly needs to be portable.  Batch/CMD files 
also seem useful on WINDOWS. And Powershell?

If a launcher is developed for or enhanced for other systems, shell 
scripts may be useful, and Batch/CMD not.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20150213/543ea63d/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2015-February/138210.html below:

[Python-Dev] PEP 370 - per-user scripts directory on Windows