Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCHv3 1/3] python-backports-abc: initial recipe for version 0.4 RDEPENDS
Date: Fri, 3 Jun 2016 07:03:22 +0200	[thread overview]
Message-ID: <57510F9A.8080400@mlbassoc.com> (raw)
In-Reply-To: <20160602182641.GX7939@vctlabs.com>

On 06/02/2016 08:26 PM, S. Lockwood-Childs wrote:
> Tornado 4.3 needs a couple more backport modules to prevent tornado/gen.py
> from bombing on import errors when running on python2 rather than python3.4
>
>    ImportError: No module named backports_abc
>
> Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com>

In my mind, this patch (and its sibling) don't really have anything to to
with Tornado, they are just new packages being added to make that package happy.
I'd prefer to see a commit message that reflects what this package is as well
as why it is being added.

> ---
>   .../python/python-backports-abc_0.4.bb                 | 18 ++++++++++++++++++
>   1 file changed, 18 insertions(+)
>   create mode 100644 meta-python/recipes-devtools/python/python-backports-abc_0.4.bb
>
> diff --git a/meta-python/recipes-devtools/python/python-backports-abc_0.4.bb b/meta-python/recipes-devtools/python/python-backports-abc_0.4.bb
> new file mode 100644
> index 0000000..6a4d267
> --- /dev/null
> +++ b/meta-python/recipes-devtools/python/python-backports-abc_0.4.bb
> @@ -0,0 +1,18 @@
> +SUMMARY = "collections.abc from Python 3.4"
> +DESCRIPTION = "A backport of recent additions to the 'collections.abc' module"
> +
> +LICENSE = "PSF"
> +LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=dd98d01d471fac8d8dbdd975229dba03"
> +
> +# pypi package doesn't have valid entry for license
> +SRC_URI += "https://raw.githubusercontent.com/cython/backports_abc/master/LICENSE;name=license"
> +
> +SRC_URI[md5sum] = "0b65a216ce9dc9c1a7e20a729dd7c05b"
> +SRC_URI[sha256sum] = "8b3e4092ba3d541c7a2f9b7d0d9c0275b21c6a01c53a61c731eba6686939d0a5"
> +SRC_URI[license.md5sum] = "dd98d01d471fac8d8dbdd975229dba03"
> +SRC_URI[license.sha256sum] = "0a4f3b38055f50f047a42521568fa6ddb9a5976c2884f6ae138796d0f71150ca"
> +
> +
> +
> +PYPI_PACKAGE = "backports_abc"
> +inherit pypi setuptools
>


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2016-06-03  5:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 18:24 [meta-python][PATCHv3 0/3] Tornado 4.3 is missing python2 RDEPENDS S. Lockwood-Childs
2016-06-02 18:26 ` [meta-python][PATCHv3 1/3] python-backports-abc: initial recipe for version 0.4 RDEPENDS S. Lockwood-Childs
2016-06-03  5:03   ` Gary Thomas [this message]
2016-06-03  5:38     ` S. Lockwood-Childs
2016-06-03  5:47       ` Gary Thomas
2016-06-03  5:55         ` S. Lockwood-Childs
2016-06-02 18:27 ` [meta-python][PATCHv3 2/3] python-singledispatch: initial recipe for version 3.4.0.3 S. Lockwood-Childs
2016-06-02 18:28 ` [meta-python][PATCHv3 3/3] python-tornado: add missing python2 runtime deps S. Lockwood-Childs
2016-06-02 18:58   ` S. Lockwood-Childs
2016-06-02 19:43     ` Martin Jansa

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=57510F9A.8080400@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox