Python plugin byte compiling

[tonysimpson]

I’ve created a pull request to remove the --no-compile flag from pip install in the python plugin which will mean packages will have .pyc files generated. This should mean python snaps start faster.

Remove legacy --no-compile option given to pip

[ogra]

… it also means you make the binary snaps architecture specific, and can not use something like:

architectures:
  - build-on: amd64
    run-on: all

anymore, since you now ship precompiled binaries instead of interpreted code.

Architectures

By default, Snapcraft builds a snap to run on the same architecture as the build environment. This behaviour can be modified with the top-level keywords architectures and platforms in the snap’s snapcraft.yaml. The architectures and platforms keywords are used to create a build plan. See build plans for an explanation of how build plans are created. The keywords are base-dependent: platforms is used for core24 snaps architectures is used for core20 and core22 snaps How to create a snap for …

[sparkiegeek]

https://stackoverflow.com/questions/30443490/is-pyc-platform-independent are you sure about that?

[ogra]

i totally was ! until you replied … thanks for correcting me

[sergiusens]

Instead of removing it completely, can you make this the default but add an option to the plugin to not compile… we have build-attributes for things that are generic, but I am not sure it fits there, it might.

If you feel creative, propose something or validate the use of build-attributes: [no-compile], no-compile is not to indicative enough for it to be used generically though, unless I am overthinking this.