From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: benjamin.esquivel@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] oetest.py: Add command line parameter support for tag in testexport
Date: Mon, 4 Jul 2016 14:27:51 -0500 [thread overview]
Message-ID: <577AB8B7.70808@linux.intel.com> (raw)
In-Reply-To: <006601d1d606$d2c5eef0$7851ccd0$@linux.intel.com>
On 07/04/2016 10:14 AM, Benjamin Esquivel wrote:
> Hello Mariano, comments below
>
>> class ExportTestContext(RuntimeTestContext):
>> - def __init__(self, d, target, exported=False):
>> + def __init__(self, d, target, exported=False, *args, **kwargs):
> Is the use of kwargs necessary? If not, it would be preferable to have a
> Named var here instead. Kwargs breaks readability.
Is not really necessary at this point. The idea here was to be easier to
extend the class in child classes, but I see your point with the kwargs
being to generic.
>> target.exportStart()
>> - tc = ExportTestContext(d, target, True)
>> + tc = ExportTestContext(d, target, True, **kwargs)
> If you don't want to mess with the inputs of this function by using kwargs
> then you can consider passing an object that includes the variables you want. I'd
> only suggest it if this function signature will grow.
>
Right now, it just require a single variable that is an argument from
the cli, so I will use a dict for that purpose, per our discussion.
--
Mariano Lopez
prev parent reply other threads:[~2016-07-04 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1467610017.git.mariano.lopez@linux.intel.com>
2016-07-04 5:28 ` [PATCH 1/1] oetest.py: Add command line parameter support for tag in testexport mariano.lopez
2016-07-04 15:14 ` Benjamin Esquivel
2016-07-04 19:27 ` Mariano Lopez [this message]
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=577AB8B7.70808@linux.intel.com \
--to=mariano.lopez@linux.intel.com \
--cc=benjamin.esquivel@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 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.