From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python-flask: bump to version 0.12
Date: Thu, 26 Jan 2017 12:59:21 +1300 [thread overview]
Message-ID: <20170126125921.66cc8f8e@free-electrons.com> (raw)
In-Reply-To: <20170125145021.5a2sw6ha7yewpkqw@ed>
Hello,
On Wed, 25 Jan 2017 15:50:21 +0100, Lionel Flandrin wrote:
> I'll test your patch ASAP but regarding mitsuhiko's comment in the
> github issue:
>
> @thmo these files are not imported so that is not an
> issue. Bytecompilation is supposed to skip over files it cannot byte
> compile as a result of this. pip does this correctly.
>
> Doesn't this mean that it'd be better to patch buildroot's bytecompile
> code to gracefully handle this situation by mimicking pip's behaviour
> in this situation?
I think it was on purpose that our byte compilation process actually
aborts when there is a failure. Otherwise real issues remain unnoticed.
I believe this pip behavior is actually pretty terrible.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-25 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 9:01 [Buildroot] [PATCH 1/2] python-flask: bump to version 0.12 Lionel Flandrin
2017-01-25 9:01 ` [Buildroot] [PATCH 2/2] DEVELOPERS: Add Lionel FLandrin for package/flask Lionel Flandrin
2017-01-27 8:01 ` Thomas Petazzoni
2017-01-25 9:09 ` [Buildroot] [PATCH 1/2] python-flask: bump to version 0.12 Yegor Yefremov
2017-01-25 9:18 ` Lionel Flandrin
2017-01-25 9:46 ` Yegor Yefremov
[not found] ` <20170125095858.x6lh5xjwby5lav3m@ed>
2017-01-25 10:11 ` Yegor Yefremov
2017-01-25 10:22 ` Lionel Flandrin
2017-01-25 10:24 ` Yegor Yefremov
2017-01-25 12:16 ` Lionel Flandrin
2017-01-25 12:52 ` Yegor Yefremov
2017-01-25 13:02 ` Lionel Flandrin
2017-01-25 14:19 ` Yegor Yefremov
2017-01-25 14:50 ` Lionel Flandrin
2017-01-25 23:59 ` Thomas Petazzoni [this message]
2017-01-26 12:18 ` Lionel Flandrin
2017-01-27 8:01 ` Thomas Petazzoni
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=20170126125921.66cc8f8e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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