Bug#262580: gdesklets: does not conform to python packaging policy

Nicolas Chauvat Nicolas Chauvat <nico@logilab.fr>, 262580@bugs.debian.org
Sun, 1 Aug 2004 21:57:50 +0200


On Sun, Aug 01, 2004 at 12:06:12AM +0200, Sebastien Bacher wrote:
> Le samedi 31 juillet 2004 =E0 23:33 +0200, Nicolas Chauvat a =E9crit :
> > /usr/share/doc/python/python-policy.html/
>=20
> Any particular point in mind ?=20

Oops. Forgive me for not being more precise in my bug report, it seemed
so obvious to me that i didn't make clear what i was thinking about.

Reading "3.1.1 Programs Shipping Private Modules", I realize that what I
was considering like the only way to package a python program actually
has an alternative described in the python policy.

According to this section, gdesklets can store its code in /usr/share/gde=
sklets
if it would otherwise pollute the sys.path.

My opinion is that things are easier to find and experiment with when
the executable is a simple "from gdesklets.main import run; run(sys.argv)=
"
and all the code is a python library available from=20
/usr/lib/pythonX.Y/site-packages

In other words, my opinion is that gdesklets does not pollute the sys.pat=
h,
that it is useful as a library and that I would hence prefer to have it
in /usr/lib/pythonX.Y/site-packages so that I can import it in other
programs without adding /usr/share/gdesklets to my PYTHONPATH.

The question becomes... do other, including you as a package maintainer, =
would=20
share the same opinion :-)


--=20
Nicolas Chauvat

logilab.fr - services en informatique avanc=E9e et gestion de connaissanc=
es =20