Hi all,
I have been successfully deploying my own python package with distutils
for some time now, but lately, with Python 2.4, the build_scripts
command has been behaving badly. In the part where it is supposed to
adjust the first line of the script it now produces
#!None
instead of
#!/wherev
Thanks Albert.
I already do use #!/usr/bin/env python in my package directory, but the
build_scripts part of "setup.py install" changes this line to #!None
before copying to my bin directory.
Cheers,
Cory.
Albert Hofkamp wrote:
On Wed, 12 Jan 2005 10:09:03 +0000, Cory Davis <[EM
Hi Christopher
distutils should replace that first line with the location of the
binary used to run setup.py. Are you running setup with the following
command line?
python setup.py install
Yes.
A possible complication is that I also have python 2.3.? on that
machine, which I am reluctant to remove
Thanks for the help Chris. I tried the -E option, and also installing as
root with no change - the scripts in the bin directory still end up with
#!None on the first line. Next step is to reinstall Python 2.4, and if
that doesn't work I'll just stick with 2.3.4.
Cheers,
Cory.
Christopher De Vr
Problem solved. I was actually using scipy_distutils and not distutils,
without good reason. Changing setup.py to use distutils made the
problem go away.
Cory.
Cory Davis wrote:
Hi all,
I have been successfully deploying my own python package with distutils
for some time now, but lately
