Message19537
When a script is installed on Unix, it should be named
something like "mailman-discard", with no extension.
When it is installed on Windows, it should be named
"mailman-discard.py", so that it is associated with
Python. I think that "scripts" should be smart enough
to handle this.
My suggestion is that "scripts" should be set to a list
of the scripts, including the extension, and that
distutils will remove the extension when it installs
programs on platforms where this is true:
os.name == 'posix'
It is possible to override the install_scripts class to
get this behaviour, but if you want to make a binary
distribution you also have to override bdist_wininst,
et c, since the install_scripts class is used on the
host system while building a directory tree that will
later be installed on the target system. See this
example script:
http://cvs.lysator.liu.se/viewcvs/viewcvs.cgi/mailman-discard/setup.py?rev=1.2&cvsroot=mailman-discard&content-type=text/vnd.viewcvs-markup
Peter Åstrand also suggests that on Windows, you should
create a command file named "mailman-discard.cmd" and
put it in the same directory as the
"mailman-discard.py" file. It should contain a single
line:
start %~dp0\mailman-discard.py
That way, you will be able to start the script from a
dos shell, and not just by double-clicking it in a file
browser. It would be nice if Distutils created this
file automatically when installing on the win32 platform. |
|
Date |
User |
Action |
Args |
2007-08-23 14:19:09 | admin | link | issue870479 messages |
2007-08-23 14:19:09 | admin | create | |
|