Added support to solve the infamous "we want .py on Windows, no

extension elsewhere" problem, while also bypassing the need for PATHEXT
on Windows, and in fact the need to even write script files at all, for
any platform.  Instead, you define "entry points" in your setup script,
in this case the names of the scripts you want (without extensions) and
the functions that should be imported and run to implement the scripts.
Setuptools will then generate platform-appropriate script files at
install time, including an .exe wrapper when installing on Windows.

--HG--
branch : setuptools
extra : convert_revision : svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/sandbox/trunk/setuptools%4041246

1 files changed, 5 insertions, 5 deletions

diff --git a/setuptools/command/develop.py b/setuptools/command/develop.py
index 1eb8bf6b..24875467 100755
--- a/setuptools/command/develop.py
+++ b/setuptools/command/develop.py
@@ -101,6 +101,11 @@ class develop(easy_install):
             return easy_install.install_egg_scripts(self,dist)
 
         # create wrapper scripts in the script dir, pointing to dist.scripts
+
+        # new-style...
+        self.install_console_scripts(dist)  
+
+        # ...and old-style
         for script_name in self.distribution.scripts or []:
             script_path = os.path.abspath(convert_path(script_name))
             script_name = os.path.basename(script_path)
@@ -116,8 +121,3 @@ class develop(easy_install):
 
 
 
-
-
-
-
-