I think those ports should be converted to USES=python , you don't want to have to touch 100 ports everytime you expire a python3.x port

In D34739#895706, @bapt wrote:

To be honnest I am not convinced we should pursue in that direction, only debian seems to be doing something like that and they use a python script to compile and cleanup called by a trigger. All other OSes I have checked are not at all doing anything in that direction.

I am personnally not seeing what problem does this approarch solves vs the complexity it adds, at least this needs to be clarified.

In my opinion, not knowing much about the python ecosystem, it seems better to implement something in the port framework to ensure we have all the cache generated at packaging time, rather that generated via a hook.

There are still lua errors, for instance

Please don't do this.
This has to be fixed in the framework, not in individual ports.

These 2 changes (no-compile / bytecode trigger) must be seperate commits and seperate exp-runs.

In D34739#883579, @vishwin wrote:

now that we apparently have to appease non-fatal errors not part of the build, as if package builders are sentient beings

py39-sphinx package seems to exhibit some bug in the trigger