Philip Brown <[email protected]> wrote: > I just discovered that debian has an explicit, separate > "python policy". > Thought I'd reference it here. > > http://www.debian.org/doc/packaging-manuals/python-policy/ > > As usual.. while we are not bound to follow everything debian does... we > would be fools not to learn from their amassed experience on the subject. > > And coincidently, their policy on .pyc files can be found at > http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-bytecompilation > > "If a package provides any binary-independent modules (foo.py files), the > corresponding bytecompiled modules (foo.pyc files) and optimized modules > (foo.pyo files) must not ship in the package. Instead, they should be > generated in the package's postinst, and removed in the package's prerm. "
What is the reason for such a decision? Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
