tahoe-lafs/setup.py
Zooko O'Whielacronx 4b4f5bbcba change #!/usr/bin/python to #!/usr/bin/env python
Note that using "whatever version of python the name 'python' maps to in the current shell environment" is more error-prone that specifying which python you mean, such as by executing "/usr/bin/python setup.py" instead of executing "./setup.py".  When you build tahoe (by running "make") it will make a copy of bin/allmydata-tahoe in instdir/bin/allmydata-tahoe with the shebang line rewritten to execute the specific version of python that was used when building instead of to execute "/usr/bin/env python".

However, it seems better that the default for lazy people be "whatever 'python' means currently" instead of "whatever 'python' meant to the manufacturer of your operating system".
2007-03-29 14:01:28 -07:00

23 lines
553 B
Python

#! /usr/bin/env python
from distutils.core import setup
from distutils.core import Extension
from distutils.command.build_ext import build_ext
import os, sys
setup(
name="AllMyData",
version="0.0.1",
packages=["allmydata", "allmydata.test", "allmydata.util",
"allmydata.filetree", "allmydata.scripts",
],
package_dir={ "allmydata": "src/allmydata",
},
scripts = ["bin/allmydata-tahoe"],
package_data={ 'allmydata': ['web/*.xhtml'] },
description="AllMyData (tahoe2)",
)