Message120864
I have the following setup.py script:
#!/usr/bin/env python
from distutils.core import setup
scripts=["hello.py"]
setup(scripts=scripts)
I have two different python installations (using virtualenv) where I
wish to install this program. So I do
~/tmp/test_setup/python1/bin/python setup.py install
which creates a file at
/users/geoff/tmp/test_setup/python1/bin/hello.py, that looks like
this:
#!/users/geoff/tmp/test_setup/python1/bin/python
print "Hello"
So far so good. But then I also install it somewhere else:
~/tmp/test_setup/python2/bin/python setup.py install
which creates a file at
/users/geoff/tmp/test_setup/python2/bin/hello.py which refers to
"python1", i..e it has the same contents as the first one. Which is
clearly not what I want.
The cached script in the build tree appears not to get updated once it exists. |
|
Date |
User |
Action |
Args |
2010-11-09 13:11:29 | gjb1002 | set | recipients:
+ gjb1002, tarek, eric.araujo |
2010-11-09 13:11:29 | gjb1002 | set | messageid: <1289308289.62.0.579780588392.issue10374@psf.upfronthosting.co.za> |
2010-11-09 13:11:28 | gjb1002 | link | issue10374 messages |
2010-11-09 13:11:27 | gjb1002 | create | |
|