python3.2+ compiled files

Jeff Johnson n3npq at mac.com
Sat Apr 9 21:26:46 CEST 2011


On Apr 9, 2011, at 2:13 PM, Patryk Zawadzki wrote:

> 2011/4/9 Elan Ruusamäe <glen at pld-linux.org>:
>> so my vote goes for keeping the old .py[co] method, and perhaps change to
>> make is package only .pyc, it is rather ratre somebody invokes python with
>> -O option so the .pyo is to be needed. or why it was packaged in first
>> place? to get files owned in case somebody invokes as root and .pyo gets
>> created? perhaps package .pyc as regular files and .pyo as ghosted then.
> 
> Not sure about PLD but I suppose we just followed what the others were
> doing. Other distros did it this way so they could set proper selinux
> attributes.
> 

Yes. Attaching SElinux xattr's to 1+ M paths forced *.pyo to be included
everywhere/always in *.rpm.

That *was* 5+ years ago. There's no known reason why xattr's can't be done
in other ways. In fact SELinux does relabeling outside of rpm these
days, there's literally no reason that *.pyo MUST be included in *.rpm
5+ years later.

And 5+ years later SELinux hasn't really achieved the wide deployment desired,
packaging *.pyc and adapting to changing conventions in pyton > 3.2 wasn't
even conceivable 5+ years ago.

73 de Jeff

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4645 bytes
Desc: not available
URL: </mailman/pipermail/pld-devel-en/attachments/20110409/8578a3a3/attachment.p7s>


More information about the pld-devel-en mailing list