From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: lw@hqv.ch, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] python3: Allow to specify which pyc files to keep
Date: Thu, 10 Apr 2025 12:58:30 +0100 [thread overview]
Message-ID: <ff2d65f3242dec409f8ed3bce874622d396ed88c.camel@linuxfoundation.org> (raw)
In-Reply-To: <13400.1744285010599994886@lists.openembedded.org>
On Thu, 2025-04-10 at 04:36 -0700, Lukas Woodtli via lists.openembedded.org wrote:
>
> > Should we rather just package the higher level .pyc into their own packages?
>
>
> But this would include 3 additional packages. One for each optimization level.
> Embedded devices might have limited storage resources.
> Therefore, it makes sense to just include the .pyc files with the necessary optimization level to the image.
> And not all of them.
The nice thing with packages is that you can then choose to install
them or not. We'd want to default to not for these.
The key question is whether this level of configuration is generally
useful enough to be worth us maintaining it in OE-Core. I don't know if
this is something you needed for a one off investigation or that people
need it in general.
Cheers,
Richard
next prev parent reply other threads:[~2025-04-10 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 6:37 python3: Allow to specify which pyc files to keep Lukas Woodtli
2025-04-10 8:02 ` [OE-core] " Alexander Kanavin
2025-04-10 11:36 ` Lukas Woodtli
2025-04-10 11:58 ` Richard Purdie [this message]
2025-04-10 12:11 ` [OE-core] " Alexander Kanavin
2025-04-10 13:05 ` Lukas Woodtli
2025-04-10 14:31 ` [OE-core] " Alexander Kanavin
2025-04-11 8:55 ` Mike Looijmans
2025-04-17 9:19 ` Lukas Woodtli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff2d65f3242dec409f8ed3bce874622d396ed88c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=lw@hqv.ch \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox