When writing the setup script for a distribution, section 3.4 explains:

3.4 Installing Scripts

So far we have been dealing with pure and non-pure Python modules, which are usually not run by themselves but imported by scripts.

Scripts are files containing Python source code, intended to be started from the command line. Scripts don't require Distutils to do anything very complicated. The only clever feature is that if the first line of the script starts with #! and contains the word ``python'', the Distutils will adjust the first line to refer to the current interpreter location. 

The scripts option simply is a list of files to be handled in this way. From the PyXML setup script: 


setup (...
       scripts = ['scripts/xmlproc_parse', 'scripts/xmlproc_val']
      )

Unfortunately, this doesn't work with sdist unless you ALSO create a manifest.in file. Otherwise, it silently ignores the scripts listed in setup. bdist works just fine, so it's apparently something wrong in sdist.

Please fix this. Thank you.

Anna Ravenscroft

Logged In: YES 
user_id=3066

This is fixed on the trunk as
Lib/distutils/command/build_scripts.py 1.22 and sdist.py 1.57.

I'm not entirely sure this should be backported for Python
2.3.x, but it probably should be.

Logged In: YES 
user_id=3066

Added note about inclusion of scripts in Doc/dist/dist.tex
revision 1.73.  This should be back-ported along with the
actual fix.

Logged In: YES 
user_id=3066

Backported for Python 2.3.4 as:

Lib/distutils/command/build_scripts.py  1.21.8.1
Lib/distutils/command/sdist.py  1.56.14.1
Doc/dist/dist.tex  1.56.8.5