qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: python3 script header and rhel8
Date: Tue, 28 Jan 2020 16:58:43 +0100	[thread overview]
Message-ID: <cfa26656-8202-bb0c-fc91-e53b2d89976c@redhat.com> (raw)
In-Reply-To: <2cb797a9-25ec-8b36-2268-ec9638b14e1e@virtuozzo.com>

On 1/28/20 4:44 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
> 
> Hmm Qemu dropped support for python2, and anyway python2 is not supported now at all.
> 
> Still, we have a lot of "#!/usr/bin/env python" headings in our scripts, which is
> unsupported by rhel8 by default. So, for example, because of such line in
> tests/qemu-iotests/nbd-fault-injector.py, iotest 277 fails.
> 
> Of course, it's simple to set python in rhel8 to be python3... But should we fix
> all the headings to be "#!/usr/bin/env python3"? Or what is the correct heading
> for scripts in a new python3 world?

I'd go for a codebase wide cleanup for once, and use python3. That way 
we are ready for when Python4 goes out, we won't suffer the same pain. 
That also mean we'll have to explicitly support Python4.

Eventually add modify scripts/checkpatch.pl to refuse commits 
introducing unversioned python back.



  reply	other threads:[~2020-01-28 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 15:44 python3 script header and rhel8 Vladimir Sementsov-Ogievskiy
2020-01-28 15:58 ` Philippe Mathieu-Daudé [this message]
2020-01-28 16:07 ` Daniel P. Berrangé
2020-01-28 21:51   ` John Snow
2020-01-29 15:58   ` Stefan Hajnoczi

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=cfa26656-8202-bb0c-fc91-e53b2d89976c@redhat.com \
    --to=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).