On 12/18/2017 06:15 PM, Mark Asselstine wrote:
On Mon, Dec 18, 2017 at 10:36 AM, Christopher Larson <[email protected]> wrote:
All our python recipes should be explicitly listing the python module
packages they require. No python module recipes should be depending on
python-modules or python3-modules, but explicitly what they require.
This is a giant PITA for little gain in my opinion. The typical python
'vehicles' to define dependencies, things like setup.py, requires.txt,
requirements.txt..., never bother to list stdlibs. These are standard
libs that are just expected to be there. If a system is being
installed with only select python modules it will behave differently
than python found on any other system violating the rule of least
surprise. On top of this most of these modules are ~40K in size and
there are roughly 60 in the stdlib so the size gain in installing a
few vs. all of them is extremely negligible. All of this seems to add
way more work and churn that outweighs any real benefit.
I tend to agree with this. Add also the situation that the yocto project
needs to upgrade oe-core to python 3.6 as soon as possible, and to 3.7
soon after, no one has enough time to do this rather non-trivial job,
and I'm beginning to wonder if the best way out is to remove the module
splitting altogether, and write a clean, simple and maintainable python3
recipe from scratch with minimal amount of custom patching and hopefully
no write-only hacks.
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
