On Tue, Nov 9, 2010 at 6:31 AM, Tarek Ziadé wrote:
> Or... keep in that configure file the path to the interpreter and just
> rebuild all scripts in case the interpreter has changed.
+1 to the simple approach.
Given the need to do this, I guess I don't really see the value of
storing scripts in
On Tue, Nov 9, 2010 at 12:04 PM, Fred Drake wrote:
> On Tue, Nov 9, 2010 at 5:58 AM, Geoff Bache wrote:
>> Is this a bug?
>
> I think so.
>
>> Or have I missed something in my setup.py? It works of
>> course if I remove the generated "build" directory by hand, but it's
>> not so nice to have to r
Hi Tarek,
> Can you add an issue in bugs.python.org please (using the "Distutils2"
> component and "feature request")
I've added a bug, but felt I had to describe it as I saw it (i.e. a
behaviour issue
with Distutils). It took me quite some time to track down what was going on,
and I didn't think
On Tue, Nov 9, 2010 at 11:58 AM, Geoff Bache wrote:
> Hi all,
>
> 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 t
On Tue, Nov 9, 2010 at 5:58 AM, Geoff Bache wrote:
> Is this a bug?
I think so.
> Or have I missed something in my setup.py? It works of
> course if I remove the generated "build" directory by hand, but it's
> not so nice to have to remember to do that.
You should be able to remove the build/ d
Hi all,
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
