From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 26 Jan 2017 12:59:21 +1300 Subject: [Buildroot] [PATCH 1/2] python-flask: bump to version 0.12 In-Reply-To: <20170125145021.5a2sw6ha7yewpkqw@ed> References: <20170125091854.2kwm43d3ncxbfdhp@ed> <20170125095858.x6lh5xjwby5lav3m@ed> <20170125102228.ykcq4xsa5xnp7yar@ed> <20170125121659.5eaex6iynmrbrxb4@ed> <20170125130241.5jwsxvs67a5qd2xc@ed> <20170125145021.5a2sw6ha7yewpkqw@ed> Message-ID: <20170126125921.66cc8f8e@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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