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

[Andreas Oberritter <obi@opendreambox.org>]

On Thu, 17 Aug 2017 03:24:23 -0700
Alejandro Hernandez <alejandro.hernandez@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.

Best regards,
Andreas

P.S.: I didn't see patches 2 and 3. Is it just an incorrect subject?