[csw-maintainers] debian's python policy

[Philip Brown]

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. "


Also of interest:

" The file /etc/python/debian_config allows configuration how modules should
  be byte-compiled. The postinst scripts should respect these settings."

So, us having a class handle this kind of thing, is strongly indicated as a
positive thing for future enhancements such as that.