Issue 60: Implemented experimental opt-in support for using native launchers rather than installing launcher executables. My initial experience with this technique has been very positive.

1 files changed, 9 insertions, 0 deletions

diff --git a/docs/easy_install.txt b/docs/easy_install.txt
index 12bc73ea..92e770b7 100644
--- a/docs/easy_install.txt
+++ b/docs/easy_install.txt
@@ -96,6 +96,15 @@ sections below on `Command-Line Options`_ and `Configuration Files`_.  You
 can pass command line options (such as ``--script-dir``) to
 ``ez_setup.py`` to control where ``easy_install.exe`` will be installed.
 
+Setuptools also supports deferring to an external launcher such as
+`pylauncher <https://bitbucket.org/pypa/pylauncher>`_ for launching scripts.
+Enable this experimental functionality by setting the
+``SETUPTOOLS_USE_PYLAUNCHER`` environment variable. Setuptools will then not
+install its own launcher executable, but will install scripts as simple
+scripts with a .py (or .pyw) extension appended. If these extensions are
+associated with the pylauncher and listed in the PATHEXT environment variable,
+these scripts can then be invoked simply and directly just like any other
+executable.
 
 
 Downloading and Installing a Package