From: Henning Heinold <heinold@inf.fu-berlin.de>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [OE-core] PLEASE READ: Major change landing shortly (python whitespace)
Date: Thu, 19 Jul 2012 10:26:13 +0200 [thread overview]
Message-ID: <20120719082613.GA5979@mi.fu-berlin.de> (raw)
In-Reply-To: <20120718214358.GT22569@jama.jama.net>
On Wed, Jul 18, 2012 at 11:43:58PM +0200, Martin Jansa wrote:
> On Wed, Jul 18, 2012 at 12:40:18PM +0100, Richard Purdie wrote:
> > On Wed, 2012-07-18 at 11:17 +0100, Burton, Ross wrote:
> > > On 18 July 2012 11:06, Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > > I put a proposal to the TSC, that we have bitbake warn/error whenever it
> > > > finds tab characters in any python function. The advantage of this is
> > > > that we give the user a clear definitive error. The downside is that
> > > > we'll have to go through all the metadata and scrub it for the problem.
> > >
> > > Have you ran that warning over oe-core to check that there are not any
> > > legitimate uses of \t, not for indentation but inside strings? I
> > > can't think of any realistic use but you never know (construct a
> > > Makefile in a python function?).
> >
> > The check is for actual tab characters, not "\t". There are some
> > legitimate users of tab characters which I've replaced with \t in
> > strings.
> >
> > My current patch work in progress for the conversion is:
> >
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/t14&id=49d3d01f3d61a0eb19b6852229fa8fc26712f653
>
> Would be great if someone updates
>
> bitbake/contrib/vim to highlight tabs, so that every tab would be easily
> spotted in recipe/bbclass.
>
> And maybe also meta-openembedded/contrib/oe-stylize.py, but that seems
> to expand tabs to spaces already.
>
> Cheers,
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
Hi,
should we enable the vim unwanted spaces/tabs higlighting too?
Bye Henning
next prev parent reply other threads:[~2012-07-19 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 10:06 PLEASE READ: Major change landing shortly (python whitespace) Richard Purdie
2012-07-18 10:17 ` [OE-core] " Burton, Ross
2012-07-18 11:40 ` Richard Purdie
2012-07-18 21:43 ` Martin Jansa
2012-07-19 8:26 ` Henning Heinold [this message]
2012-07-19 9:49 ` Martin Jansa
2012-07-19 10:15 ` Richard Purdie
2012-07-19 11:18 ` Martin Jansa
2012-07-19 11:27 ` Martin Jansa
2012-07-18 10:40 ` Martin Jansa
2012-07-18 13:11 ` Richard Purdie
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=20120719082613.GA5979@mi.fu-berlin.de \
--to=heinold@inf.fu-berlin.de \
--cc=bitbake-devel@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox