On Mon, Apr 16, 2012, at 16:59, Allan McRae wrote:
>
>
> I'd consider using "#!/usr/bin/evn python" over "#!/usr/bin/python" a
> feature and not a bug as it allows me to put a local version of python
> earlier in my path to test bugfixes etc. So I would actually vote to
> switch all the #! to
On 16/04/12 16:41, Ralf Schmitt wrote:
> Martti Kühne writes:
>
>> On Mon, Apr 16, 2012 at 12:25:39AM +0200, Ralf Schmitt wrote:
>>>
>>> that's what I think. upstream in this case is archlinux.
>> no. [1] is upstream.
>
> ok. I have something like 20 broken shebangs in /usr/bin. I won't
> contac
Martti Kühne writes:
> On Mon, Apr 16, 2012 at 12:25:39AM +0200, Ralf Schmitt wrote:
>>
>> that's what I think. upstream in this case is archlinux.
> no. [1] is upstream.
ok. I have something like 20 broken shebangs in /usr/bin. I won't
contact the authors of those packages but just fix them lo
On Mon, Apr 16, 2012 at 12:25:39AM +0200, Ralf Schmitt wrote:
>
> that's what I think. upstream in this case is archlinux.
no. [1] is upstream.
>
> distutils installs executable scripts with the full path to the python
> interpreter.
no again.
meld's source package is built with make, see [2].
Martti Kühne writes:
> On Sun, Apr 15, 2012 at 09:51:44PM +0200, Ralf Schmitt wrote:
>> Renaming would work, but I do not see that as an acceptable
>> solution. The problem is the shebang and that should be fixed.
>>
>> I really fail to see why I even have to explain that stuff. Users should
>>
On Sun, Apr 15, 2012 at 09:51:44PM +0200, Ralf Schmitt wrote:
> Renaming would work, but I do not see that as an acceptable
> solution. The problem is the shebang and that should be fixed.
>
> I really fail to see why I even have to explain that stuff. Users should
> be able to install custom inte
Martti Kühne writes:
>
> question to OP: what is it you have there in your home directory and would
> renaming the binary work for distinction?
> ~/bin/python2.6, ~/bin/python-frobtweaks
I'm using virtualenv, so I have a "copy" of the system python in my
user's home directory. Judging from the b
On Sun, Apr 15, 2012 at 12:36:09PM +0300, Mantas M. wrote:
> On 2012-04-15 07:03, Martti Kühne wrote:
> > #!/usr/bin/env python2 and #!python2 in my experience have exactly the same
> > effect, so all I can do is ask you what differences you found and then we
> > could
>
[...]
>
> The difference
On 2012-04-15 07:03, Martti Kühne wrote:
> #!/usr/bin/env python2 and #!python2 in my experience have exactly the same
> effect, so all I can do is ask you what differences you found and then we
> could
Nobody is talking about "#!python2", but about "#!/usr/bin/python2".
The former, "#!python2",
On Sat, Apr 14, 2012 at 09:01:30PM +0200, Ralf Schmitt wrote:
> Hi all,
>
> I've opened https://bugs.archlinux.org/task/28881 "meld uses wrong
> shebang" some time ago. The description reads:
>
> ,
> | meld uses "#! /usr/bin/env python2" as shebang. It should use "#!
> | /usr/bin/python2".
>
Hi all,
I've opened https://bugs.archlinux.org/task/28881 "meld uses wrong
shebang" some time ago. The description reads:
,
| meld uses "#! /usr/bin/env python2" as shebang. It should use "#!
| /usr/bin/python2".
`
The bug has been closed as "Not a bug" and "Works fine as-is". I've
tried
11 matches
Mail list logo