Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python: make python2 and python3 alternatives to python
Date: Thu, 13 Apr 2017 13:18:42 +0300	[thread overview]
Message-ID: <e2a6b8d9-5c53-29c2-0ee2-810e83fefc86@linux.intel.com> (raw)
In-Reply-To: <85c346c4-f6d6-c853-bfc5-0daa64ea2db8@linux.intel.com>

On 04/13/2017 01:15 PM, Alexander Kanavin wrote:
> On 04/13/2017 11:33 AM, Dmitry Rozhkov wrote:
>> If only python3 is installed on an image nothing provides
>> /usr/bin/python even though many scripts compatible with
>> both python2 and python3 just state `#!/usr/bin/env python`
>> in their shebang line.
>>
>> Make python and python3 recipes provide alternatives for
>> /usr/bin/python and /usr/bin/python-config. By default
>> python2 has higher priority over python3.
>
> This runs against upstream recommendation and common distro practice.
> And it will break scripts that have not been ported to Python 3. Please
> fix the scripts instead to refer to python 3 whenever possible.

Also, if there are scripts on the image that refer to 'python', yet 
python 2.7 is not installed into the image, that's a missing RDEPENDS in 
the scripts recipe.

Alex



  reply	other threads:[~2017-04-13 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  8:33 [PATCH] python: make python2 and python3 alternatives to python Dmitry Rozhkov
2017-04-13 10:15 ` Alexander Kanavin
2017-04-13 10:18   ` Alexander Kanavin [this message]
2017-04-13 14:47   ` Burton, Ross
2017-04-18  8:44     ` Dmitry Rozhkov
2017-04-18  9:33       ` Burton, Ross

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=e2a6b8d9-5c53-29c2-0ee2-810e83fefc86@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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