Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] About python2 and python3
Date: Mon, 9 May 2016 22:26:04 +0200	[thread overview]
Message-ID: <20160509222604.25fa27a8@free-electrons.com> (raw)
In-Reply-To: <5730F02E.6040806@gmail.com>

Hello,

On Mon, 9 May 2016 22:16:46 +0200, Marco Trapanese wrote:

> if python2 is selected is not possible to add python3.
> But python2 and python3 are quite different and sometimes is useful to 
> have both. i cannot deselect python2 because is selected by another package.

We currently do not support building both Python 2 and Python 3.

The main reason is that we allow building external Python modules, and
it would be very annoying with Kconfig to allow the user to tell which
modules should be built/installed for Python 2, which modules should be
built/installed for Python 3, and which modules should be
built/installed for both.

One possibility would be to install all of them for both Python 2 and
Python 3, but that's very inefficient.

So, I think we'll stick with just supporting the installation of either
Python 2 or Python 3. I'd rather recommend you to see why you need
Python 2 at all, and try to see if you can make that part work with
Python 3.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-09 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 20:16 [Buildroot] About python2 and python3 Marco Trapanese
2016-05-09 20:26 ` Thomas Petazzoni [this message]
2016-05-09 21:00   ` Marco Trapanese
2016-05-09 21:16     ` Thomas Petazzoni

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=20160509222604.25fa27a8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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