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:47:50 +0200 [thread overview]
Message-ID: <57511A06.3060309@mlbassoc.com> (raw)
In-Reply-To: <20160603053852.GD7939@vctlabs.com>
On 06/03/2016 07:38 AM, S. Lockwood-Childs wrote:
> On Fri, Jun 03, 2016 at 07:03:22AM +0200, Gary Thomas wrote:
>> 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.
>
>>> +SUMMARY = "collections.abc from Python 3.4"
>>> +DESCRIPTION = "A backport of recent additions to the 'collections.abc' module"
>
> What would you like to see, a repeat of the SUMMARY or DESCRIPTION lines
> added to the corresponding commit messages (if so, which)?
>
> Other than that, I don't know what else to say about them; if their absence
> wasn't breaking Tornado, I would not have picked either of these particular
> modules to submit. Neither one has much use yet outside of Tornado (found no
> other users of abc, while singledispatch is also used by rpy (python interface
> to R).
>
I would think the SUMMARY would be OK, along with a note that the package was
introduced to make Tornado happy. (I know this is just "eye candy", but it does
help when searching through git logs...)
Thanks for doing this - I was about to make similar changes myself.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-06-03 5:47 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
2016-06-03 5:38 ` S. Lockwood-Childs
2016-06-03 5:47 ` Gary Thomas [this message]
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=57511A06.3060309@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 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.