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 <[EMAIL PROTECTED]> wrote:
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
#!/whereverpythonis/python
Has anyone else encountered this?
I haven't (as I am not using 2.4 :-) )
However, there is an easy way around this, just use
#!/usr/bin env python
instead.
Albert
-- http://mail.python.org/mailman/listinfo/python-list
