Hi all, I run adequate on my system, which means I notice when Python module packages don't bytecompile when they are installed. So far I've just been ignoring the warnings that adequate prints. https://salsa.debian.org/debian/adequate In addition I noticed: * some Python modules on my system weren't bytecompiled but did bytecompile when I reinstalled them (blinker for example) * many of the Python modules on my system don't bytecompile their test directories (django for example) * relatively few packages I have installed don't bytecompile when I ignore test paths (lib2to3, tk, uno, distutils) Some questions: Should all module packages bytecompile? Should all module packages bytecompile all their directories? What are the downsides when module packages don't bytecompile? What are the downsides when module packages do bytecompile? Do we need a lintian complaint about this issue? Do we need any improvements in how module packages bytecompile? For example using triggers instead of postinst scriptlets. Any other thoughts? -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part