[csw-maintainers] debian's python policy

Mike Watters mwatters at opencsw.org
Wed May 20 20:44:44 CEST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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

This is exactly how it is built now.

> 
> 
> 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.
I will work on the class scripts for this and release it that way.

- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoUT5wACgkQLrhmsXMSLxf9PACfaL6aWlyMTYEkAMyps/C7ThGQ
LoAAnjuhun1nkUsYpCQ7QScSUJJulq26
=jn88
-----END PGP SIGNATURE-----



More information about the maintainers mailing list