From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] *.py: Replace '#!/usr/bin/python3' with '#!/usr/bin/env python3'
Date: Fri, 27 Apr 2018 09:31:56 +0800 [thread overview]
Message-ID: <5AE27D8C.3020804@cn.fujitsu.com> (raw)
In-Reply-To: <20180426105414.cugq7rstaifqnxvn@dell5510>
On 2018/04/26 18:54, Petr Vorel wrote:
> Hi Xiao,
>
>>>>> On 2018/04/26 14:45, Xiao Yang wrote:
>>>>>> If we install python3 in specific path(/usr/local/bin) rather than the
>>>>>> default(/usr/bin), the standard shebang(#!/usr/bin/python3) cannot
>>>>>> interpreter python code due to wrong path. We should use env to
>>>>>> search the correct path of python3 dynamically.
>>>>> ----------------------------------------------------------------------------
>>>>> # which python3
>>>>> /usr/local/bin/python3
>>>>> # ./in.py
>>>>> -bash: ./in.py: /usr/bin/python3: bad interpreter: No such file or directory
>>>>> ----------------------------------------------------------------------------
>>> And is it really general RHEL6.9GA problem? Isn't it installable into standard path with
>>> EPEL? [1]
>> Hi Petr,
>> Neither, i just install python3 into /usr/local/bin by Python-3.6.5.tgz on purpose. :-P
> And what prevent you to use either python34 from EPEL (which installs into standard
> /usr/bin) or symlinking your compiled python3 into /usr/bin ?
>
> Both are working solutions.
Hi Petr,
Nothing prevent me to use either python34 or symlink.
In all kinds of cases, it is possible that python3 is not installed in
the standard path. I think
we should adapt python code to enviroment instead of changing
enviroment to adapt to code.
Do you think so?
Thanks,
Xiao Yang
>> Thanks,
>> Xiao Yang
>
> Kind regards,
> Petr
>
>
> .
>
next prev parent reply other threads:[~2018-04-27 1:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 6:45 [LTP] [PATCH 1/2] *.py: Replace '#!/usr/bin/python3' with '#!/usr/bin/env python3' Xiao Yang
2018-04-26 6:45 ` [LTP] [PATCH 2/2] commands/file01: Fix "python3" match failure Xiao Yang
2018-04-26 12:15 ` Petr Vorel
2018-04-26 7:03 ` [LTP] [PATCH 1/2] *.py: Replace '#!/usr/bin/python3' with '#!/usr/bin/env python3' Xiao Yang
2018-04-26 8:06 ` Petr Vorel
2018-04-26 8:15 ` Xiao Yang
2018-04-26 8:16 ` Petr Vorel
2018-04-26 8:39 ` Xiao Yang
2018-04-26 10:54 ` Petr Vorel
2018-04-27 1:31 ` Xiao Yang [this message]
2018-04-27 14:08 ` Cyril Hrubis
2018-04-30 6:38 ` Petr Vorel
2018-05-02 15:37 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5AE27D8C.3020804@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox