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

Alejandro Hernandez alejandro.hernandez at linux.intel.com
Thu Aug 17 15:06:38 UTC 2017


Hey Andreas,


On 08/17/2017 09:14 AM, Andreas Oberritter wrote:
> On Thu, 17 Aug 2017 03:24:23 -0700
> Alejandro Hernandez <alejandro.hernandez at linux.intel.com> 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
>>     files would be created on their first run?, but they also sometimes give a
>>     magic number error and take up space, so we leave it to the user to
>>     decide if they want them or not.
> A serious problem with not shipping precompiled pyc and/or pyo files is that,
> once generated on first run, package managers won't uninstall them.
>
> This can cause many undesired effects, because python programs will still be
> able to import these files, but dependencies like graphics or shared libraries
> may have been deleted by the package manager.
>
> Also, not being able to uninstall something is bad on its own.
>
> So, if anything, I believe INCLUDE_PYCS = "1" would be the only sane default,
> unless no package management was involved at all.
>
> And no read-only filesystem, for what it's worth.
Interesting, I didn't know that happened, sounds like a fair argument,
I will make sure to set INCLUDE_PYCS = "1" by default to avoid problems
like this, and let the user set it to 0 if thats what they want.
>
> Best regards,
> Andreas
>
> P.S.: I didn't see patches 2 and 3. Is it just an incorrect subject?
Yes, there's 2 other patches, which are used for python3, but somehow
I forgot to send them, it was 4 am my apologies, will send them in a bit.

Regards,
Alejandro



More information about the Openembedded-core mailing list