Re: [Duplicity-talk] #!/usr/bin/python

[Kenneth Loafman]

tox and virtualenv handle the problem for you.  Why reinvent?

...Ken

On Sun, Oct 25, 2015 at 3:07 PM, <address@hidden> wrote:

weird sh*t. actually you already have it correctly in bazaar, but setup.py replaces it with the installing python instance.

i do not seem to find a way to disable this "feature". only way i found so far is to use setup.cfg as described here
 http://stackoverflow.com/questions/1530702/dont-touch-my-shebang

has somebody a smarter way to circumvent setup replacing our shebang?

..ede

On 25.10.2015 17:53, Kenneth Loafman wrote:
> No problem, go ahead and change it.
>
> ...Ken
>
>
> On Sun, Oct 25, 2015 at 11:20 AM, <address@hidden <mailto:address@hidden>> wrote:
>
>     hey Ken,
>
>     any specific reason why we expect python to reside in /usr/bin . just spent 5 hours try to find out why duplicity didn't like to play well with several python versions installed under /usr/local/python-<version> just to find out that the interpreter path is hardcoded after the shebang.
>
>     would you oppose a more generic
>      #!/usr/bin/env python
>     which would look up python in the current PATH env var?
>
>     ..ede
>
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.nongnu.org/mailman/listinfo/duplicity-talk

>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk