All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof.johansson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-architecture
	<openembedded-architecture@lists.openembedded.org>,
	 bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] [PATCH] build/data: Don't expand python functions before execution [API change]
Date: Tue, 2 Feb 2016 15:51:02 +0100	[thread overview]
Message-ID: <20160202145101.GV31212@axis.com> (raw)
In-Reply-To: <CAJTo0LanTJT6B4YJ6=xfetCSi882LOBAd5P0gNXeXyC=pqiJLQ@mail.gmail.com>

On 16-02-02 14:41 +0000, Burton, Ross wrote:
> On 2 February 2016 at 14:07, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
> 
> > I propose we default to not expanding python code and then deal with
> > any consequences from that if/as/where identified. This will improve
> > new user understanding and usability of the system, it also allows
> > several long standing weird expansion issues to be fixed.
> >
> 
> As someone who has had to write classes that do "$" + "{FOO}", this gets a
> massive +1 from me.

Indeed, it's a very welcome change from my point of view! +1

-- 
olofjn


  reply	other threads:[~2016-02-02 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 14:07 [PATCH] build/data: Don't expand python functions before execution [API change] Richard Purdie
2016-02-02 14:41 ` [Openembedded-architecture] " Burton, Ross
2016-02-02 14:51   ` Olof Johansson [this message]
2016-02-02 15:28 ` Christopher Larson
2016-02-03  6:06 ` Khem Raj

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=20160202145101.GV31212@axis.com \
    --to=olof.johansson@axis.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.