From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/5] binman: Show an error when a file is missing
Date: Mon, 7 Sep 2020 12:05:57 +0300 [thread overview]
Message-ID: <20200907090557.GO1891694@smile.fi.intel.com> (raw)
In-Reply-To: <CAPnjgZ0=MeLJYhDr_+Y0J6m+aJuMhhk1wfcaMqZUNdXZQxf5qQ@mail.gmail.com>
On Sun, Sep 06, 2020 at 07:43:39PM -0600, Simon Glass wrote:
> On Fri, 4 Sep 2020 at 03:33, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, Sep 03, 2020 at 07:28:53PM -0600, Simon Glass wrote:
> > > - self._pathname = tools.GetInputFilename(self._filename,
> > > - self.section.GetAllowMissing())
> > > + self._pathname = tools.GetInputFilename(
> > > + self._filename, self.external and self.section.GetAllowMissing())
> >
> > I hope you know that 'and' has a bit different semantics in Python than in C for example.
>
> I think I understand it, in the sense that 'x and y' returns y if x is
> true. Is that what you mean?
There is no boolean object involved!
"Note that neither and nor or restrict the value and type they return to False
and True, but rather return the last evaluated argument."
If x is last evaluated argument (false), it will be returned. Means that there
are possibilities to get None, False, empty container, etc as returned value of
'and'.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-07 9:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 1:28 [PATCH 0/5] edison: Support for writing an xFSTK image Simon Glass
2020-09-04 1:28 ` [PATCH 1/5] x86: Use multiple images Simon Glass
2020-09-04 9:30 ` Andy Shevchenko
2020-09-04 1:28 ` [PATCH 2/5] binman: Show an error when a file is missing Simon Glass
2020-09-04 9:33 ` Andy Shevchenko
2020-09-07 1:43 ` Simon Glass
2020-09-07 9:05 ` Andy Shevchenko [this message]
2020-09-07 13:57 ` Simon Glass
2020-09-04 1:28 ` [PATCH 3/5] binman: Support adding a U-Boot environment Simon Glass
2020-09-04 9:37 ` Andy Shevchenko
2020-09-04 1:28 ` [PATCH 4/5] x86: edison: Generate an image suitable for xFSTK Simon Glass
2020-09-04 9:39 ` Andy Shevchenko
2020-09-04 1:28 ` [PATCH 5/5] x86: edison: Add documentation for using am xFSTK image Simon Glass
2020-09-04 9:43 ` Andy Shevchenko
2020-09-04 9:46 ` [PATCH 0/5] edison: Support for writing an " Andy Shevchenko
2020-09-05 3:23 ` Simon Glass
2020-09-07 8:04 ` Andy Shevchenko
2020-09-07 13:57 ` Simon Glass
2020-09-07 14:12 ` Tom Rini
2020-09-07 14:15 ` Simon Glass
2020-09-07 15:10 ` Andy Shevchenko
2020-09-22 7:11 ` Bin Meng
2020-09-22 22:03 ` Simon Glass
2020-09-24 3:22 ` Bin Meng
2020-09-24 3:27 ` Bin Meng
2020-09-25 1:00 ` Simon Glass
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=20200907090557.GO1891694@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=u-boot@lists.denx.de \
/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