All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: "Elliott, Robert (Servers)" <elliott@hpe.com>,
	Sitsofe Wheeler <sitsofe@gmail.com>
Cc: Vincent Fu <vincentfu@gmail.com>,
	Rebecca Cran <rebecca@bsdio.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: Python scripts - /usr/bin/env python3 vs python vs python2.7
Date: Tue, 02 Jun 2020 14:31:11 +0200	[thread overview]
Message-ID: <3820489.GZLxUJoiUR@merkaba> (raw)
In-Reply-To: <CALjAwxgPF_oHQgDMr+v8y6r1AKbMUf9PKLxdctCugY4CHPy27w@mail.gmail.com>

Hi.

Sitsofe Wheeler - 28.05.20, 10:19:48 CEST:
> Given the above, I think the best thing is just to use "#!/usr/bin/env
> python3" everywhere and at least:
>
> - That's nicer to environments that don't have a python interpreter in
> /usr/bin - Nicer if you ever run the scripts in a virtualenv
> - Packagers can fix it up to whatever they like and at least the
> pattern is the same across the board

Okay, also in Debian it means I'd have to patch all the scripts then:

https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-interpreter_loc

Is there a complete list of Python scripts and especially their status 
in Fio? Are there any left that cannot work with Python 3? The mail by 
Vincent has some hints that there are.

I ask cause at some time in the future Python 2 will be removed from 
Debian. And I'd like to avoid having to patch scripts to support Python 
3 downstream.

fio: Python2 removal in sid/bullseye

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945641

Thanks,
-- 
Martin




      parent reply	other threads:[~2020-06-02 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 14:13 Python scripts - /usr/bin/env python3 vs python vs python2.7 Rebecca Cran
2020-05-26 14:32 ` Vincent Fu
2020-05-27 18:10   ` Elliott, Robert (Servers)
2020-05-28  8:19     ` Sitsofe Wheeler
2020-05-28 19:24       ` Vincent Fu
2020-05-29 20:42       ` Elliott, Robert (Servers)
2020-05-30  3:36         ` Sitsofe Wheeler
2020-06-02 12:31       ` Martin Steigerwald [this message]

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=3820489.GZLxUJoiUR@merkaba \
    --to=martin@lichtvoll.de \
    --cc=axboe@kernel.dk \
    --cc=elliott@hpe.com \
    --cc=fio@vger.kernel.org \
    --cc=rebecca@bsdio.com \
    --cc=sitsofe@gmail.com \
    --cc=vincentfu@gmail.com \
    /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.