On 10/5/18 10:29 AM, Alberto Planas Dominguez wrote:
On Thursday, October 4, 2018 5:29:20 PM CEST Michael Ströder wrote:
I typically have several long-running services and CLI tools running under separate service user accounts but using a similar set of modules. So I'd expect your approach to cost more disk space.
I think that this is indeed the case for this scenario: running the same code under different users will recreate the pyc under each user id.
Maybe I'm overlooking something but you will end up with at least same disk size being used. So the argument with cloud storage does not count at all.
Also I think that this can be resolved, using some better way to generate the first pyc in the local cache.
Compiling on-the-fly to a central location would possibly also result in security issues. So you would have to create a central pycache by byte-compiling during RPM post-install as root.
Also for security reasons I'd not want a tool to write code somewhere. It's bad practice to let a service account write code somewhere. It would seriously trigger my paranoia if someone adds rules to AppArmor profiles allowing that.
Another good point.
For me that's a show-stopper. Also .py? files shipped in RPMs at least are integrity-protected by RPM signature. Ciao, Michael. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org