[OE-core] [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging

2017-08-17 Thread Alejandro Hernandez
The reason we have a manifest file for python is that our goal is to keep python-core as small as posible and add other python packages only when the user needs them, hence why we split upstream python into several packages. Although our manifest file has several issues: - Its unorganized and har

Re: [OE-core] [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging

2017-08-17 Thread Alejandro Hernandez
Hey Andreas, On 08/17/2017 09:14 AM, Andreas Oberritter wrote: On Thu, 17 Aug 2017 03:24:23 -0700 Alejandro Hernandez wrote: - It creates a solution for users that want precompiled bytecode files (*.pyc) INCLUDE_PYCS = "1" can be set by the user on their local.conf to include such

Re: [OE-core] [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging

2017-08-17 Thread Andreas Oberritter
On Thu, 17 Aug 2017 03:24:23 -0700 Alejandro Hernandez wrote: > - It creates a solution for users that want precompiled bytecode files >(*.pyc) INCLUDE_PYCS = "1" can be set by the user on their local.conf to >include such files, some argument they get faster boot time, even when the >

[OE-core] [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging

2017-08-17 Thread Alejandro Hernandez
The reason we have a manifest file for python is that our goal is to keep python-core as small as posible and add other python packages only when the user needs them, hence why we split upstream python into several packages. Although our manifest file has several issues: - Its unorganized and har