On 01/07/2015 12:16 PM, Burton, Ross wrote:
On 7 January 2015 at 09:23, Mike Looijmans mailto:mike.looijm...@topic.nl>> wrote:
You definitely SHOULD ship the .pyc files. If they don't exist, the
interpreter is forced to re-compile the .py source, and will attempt to
write the resul
On 7 January 2015 at 09:23, Mike Looijmans wrote:
> You definitely SHOULD ship the .pyc files. If they don't exist, the
> interpreter is forced to re-compile the .py source, and will attempt to
> write the result to the filesystem. It won't cause harm, it won't fail, but
> it's very inefficient.
On Wed, 2015-01-07 at 17:32 +0800, Robert Yang wrote:
>
> On 01/07/2015 05:23 PM, Mike Looijmans wrote:
> > On 01/07/2015 09:07 AM, Richard Purdie wrote:
> >> On Tue, 2015-01-06 at 17:07 -0800, Robert Yang wrote:
> >>> We should not ship .pyc or .pyo file, but there are a few packages
> >>> ship .
On 01/07/2015 05:23 PM, Mike Looijmans wrote:
On 01/07/2015 09:07 AM, Richard Purdie wrote:
On Tue, 2015-01-06 at 17:07 -0800, Robert Yang wrote:
We should not ship .pyc or .pyo file, but there are a few packages
ship .pyc, should we:
Why should we not ship them? Doesn't python create these
On 01/07/2015 09:07 AM, Richard Purdie wrote:
On Tue, 2015-01-06 at 17:07 -0800, Robert Yang wrote:
We should not ship .pyc or .pyo file, but there are a few packages
ship .pyc, should we:
Why should we not ship them? Doesn't python create these at runtime if
they're not present? What happens
On Tue, 2015-01-06 at 17:07 -0800, Robert Yang wrote:
> We should not ship .pyc or .pyo file, but there are a few packages
> ship .pyc, should we:
Why should we not ship them? Doesn't python create these at runtime if
they're not present? What happens on a read only filesystem?
I'm sure we've had
On 01/07/2015 09:07 AM, Robert Yang wrote:
We should not ship .pyc or .pyo file, but there are a few packages
ship .pyc, should we:
1) Ignore them in package.bbclass as this patch showes ?
Or
2) Add a qa check then fix it by hand one by one ?
3) Fix it in a bbclass that python related recipes
We should not ship .pyc or .pyo file, but there are a few packages
ship .pyc, should we:
1) Ignore them in package.bbclass as this patch showes ?
Or
2) Add a qa check then fix it by hand one by one ?
Here is the list of oe-core's world build:
python-smartpm-1.4.1
nativesdk-python-smartpm-1.4.1
py
