All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dominic Sacré" <dominic.sacre@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Python 2 and Python 3 module recipes
Date: Sun, 16 Aug 2015 02:26:29 +0200	[thread overview]
Message-ID: <55CFD8B5.4000501@gmx.de> (raw)

Hi,

I'm trying to build a Python 3 application which depends on some modules
that are already packaged in OE for Python 2, but not for Python 3.
Since OE currently has virtually no Python 3 module recipes, this makes
me wonder what the best approach to create these recipes would be.

In most cases, I could just copy a Python 2 recipe, change the name from
"python-foo" to "python3-foo", and replace "inherit distutils" with
"inherit distutils3". However that would create a lot of duplication,
and might turn into a maintenance nightmare.

Do you have a suggestion what the right course of action would be? Move
most of the recipes' content to .inc files that can then be included by
both Python 2 and Python 3 recipes? Or maybe create a .bbclass that
would build both versions from the same recipe?
Is there any functionality already in place that would simplify this task?


Dominic


             reply	other threads:[~2015-08-16  0:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16  0:26 Dominic Sacré [this message]
2015-08-16  0:40 ` Python 2 and Python 3 module recipes Khem Raj
2015-08-17 18:57   ` Dominic Sacré

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=55CFD8B5.4000501@gmx.de \
    --to=dominic.sacre@gmx.de \
    --cc=openembedded-devel@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 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.