All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
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 16:08:13 +0200	[thread overview]
Message-ID: <20180427140813.GA22462@rei> (raw)
In-Reply-To: <20180426080658.GA4482@x230>

Hi!
> Couldn't it be solved by simple creating manually symlink python3 to /usr/bin ?
> I'm not against changing schebang to using env, if causing troubles.
> Cyril, what do you think?

Well if it's causing problems for our users we should go ahead and
change the shebangs to /usr/bin/env python3.

> It's funny that some distros already started removing python2 while still supported
> versions haven't properly added python3 yet :(.

That is why I think that we should avoid using python in LTP...

-- 
Cyril Hrubis
chrubis@suse.cz

  parent reply	other threads:[~2018-04-27 14:08 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
2018-04-27 14:08     ` Cyril Hrubis [this message]
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=20180427140813.GA22462@rei \
    --to=chrubis@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.