qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	David Michael <fedora.dm0@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scripts: Support building with Python 3
Date: Thu, 31 Aug 2017 14:25:26 +0100	[thread overview]
Message-ID: <20170831132526.GM17315@redhat.com> (raw)
In-Reply-To: <CAFEAcA_OHsZJd4hMtbMuaVD2QDT7H2XEPD03w8NKJ901Cj0Hcw@mail.gmail.com>

On Thu, Aug 31, 2017 at 02:19:05PM +0100, Peter Maydell wrote:
> On 31 August 2017 at 14:14, Daniel P. Berrange <berrange@redhat.com> wrote:
> > NB, some distros have already changed /usr/bin/python to point to py3
> > so all the files with #!/usr/bin/python in QEMU are already broken on
> > those distros.
> 
> This is a bug in those distros and they should fix it. Python 3
> is not Python 2 and making /usr/bin/python point to the wrong
> interpreter will have predictably bad results for their users...

Having /usr/bin/python point to py3 is what upstream Python will
eventually recommend. Some distros jumped a bit early, but the
others will eventually follow, and I don't see those early distros
moving back. 

https://www.python.org/dev/peps/pep-0394/


   "* python2 will refer to some version of Python 2.x.
    * python3 will refer to some version of Python 3.x.
    * for the time being, all distributions should ensure
      that python refers to the same target as python2.
    * however, end users should be aware that python refers
      to python3 on at least Arch Linux (that change is what
      prompted the creation of this PEP), so python should 
      be used in the shebang line only for scripts that are
      source compatible with both Python 2 and 3.
    * in preparation for an eventual change in the default
      version of Python, Python 2 only scripts should either
      be updated to be source compatible with Python 3 or 
      else to use python2 in the shebang line."

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-08-31 13:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20  5:58 [Qemu-devel] [PATCH] scripts: Support building with Python 3 David Michael
2017-08-21 14:29 ` Markus Armbruster
2017-08-30 17:09   ` Stefan Hajnoczi
2017-08-31  6:35     ` Markus Armbruster
2017-08-31 10:27       ` Peter Maydell
2017-08-31 10:47         ` Daniel P. Berrange
2017-08-31 10:55           ` Peter Maydell
2017-08-31 11:02             ` Daniel P. Berrange
2017-08-31 12:44               ` Markus Armbruster
2017-08-31 13:22                 ` Kashyap Chamarthy
2017-08-31 12:50               ` Peter Maydell
2017-08-31 12:58         ` Markus Armbruster
2017-08-31 13:14           ` Daniel P. Berrange
2017-08-31 13:19             ` Peter Maydell
2017-08-31 13:25               ` Daniel P. Berrange [this message]
2017-08-31 13:32                 ` Peter Maydell
2017-09-01 19:26             ` Max Reitz
2017-08-31 13:29           ` Peter Maydell
2017-08-30 17:15 ` Stefan Hajnoczi
2017-09-18 15:36 ` Stefan Hajnoczi
2017-10-02  6:17   ` Markus Armbruster

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=20170831132526.GM17315@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=fedora.dm0@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 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).