<div dir="auto"><div>Well, I've been able to do it just fine for the majority of packages in meta-python by myself. Since I contribute the majority of the patches and maintain the layer, I want this capability maintained in meta-python. If you plan on removing that functionality in oe-core, I'd like to have the opportunity to maintain the python recipes there as well rather than have a feature unilaterally removed. I don't consider it a burden and my customers find it valuable to split things out. <br><div class="gmail_extra"><br><div class="gmail_quote">On Dec 19, 2017 2:55 AM, "Alexander Kanavin" <<a href="mailto:alexander.kanavin@linux.intel.com">alexander.kanavin@linux.intel.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/18/2017 11:02 PM, S. Lockwood-Childs wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Dec 18, 2017 at 03:17:25PM -0500, Derek Straka wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have several customers who have optimized for space and would like to see<br>
the capability maintained unless core removes the ability to split python<br>
packages out. They also remove the *.py files in favor of *.pyo files (via<br>
a custom packaging mechanism). I have automated tests that go through the<br>
module importing on each of the meta-python packages to ensure it works on<br>
minimal python installations. When other contributors don't do provide<br>
that functionality, I either catch it when I do package update or when it<br>
breaks for one of my customers. I'm fine if you don't want to perform the<br>
checks yourself and it breaks my use case with missing dependencies, but I<br>
would prefer that you don't remove the dependencies that are currently in<br>
place. Thanks.<br>
</blockquote>
<br>
Me too -- some of my projects still use NAND for rootfs, where space is tight and<br>
ability to split out python modules is very useful. Thus it is not an unused<br>
feature, though many projects have SD/eMMC for rootfs and those ones generally<br>
will not care about it.<br>
</blockquote>
<br>
This configuration can be supported by making a custom python3-modules package that whitelists precisely the needed files. But it shouldn't be imposed on everyone else - it's a significant burden to maintain the dependencies in every single python package, and keep the splitting working correctly in core python as well.<br>
<br>
So I'd like to drop that - do keep in mind that very few people maintain oe-core (as opposed to sending occasional drive-by patches to fix specific issues raised in product development), and the headcount keeps getting smaller.<br>
<br>
Alex<br>
</blockquote></div><br></div></div></div>