Re: pure python modules - Python Policy 2.2.3

2002-01-13 Thread Torsten Landschoff
On Sun, Jan 13, 2002 at 09:32:58PM +0100, Matthias Klose wrote: > > If you ask me, scripts for that should go into the python package so > > that not every python-xxx package has to carry them itself. Something > > like /usr/lib/python/new-module $(pkgname) should do all the > > preprocessing. >

Re: pure python modules - Python Policy 2.2.3

2002-01-13 Thread Matthias Klose
Torsten Landschoff writes: > On Sun, Jan 13, 2002 at 03:48:40PM +0100, Bastian Kleineidam wrote: > > I have untested scripts python.postinst and python.prerm for this. > > If you ask me, scripts for that should go into the python package so > that not every python-xxx package has to carry them its

Re: pure python modules - Python Policy 2.2.3

2002-01-13 Thread Torsten Landschoff
On Sun, Jan 13, 2002 at 03:48:40PM +0100, Bastian Kleineidam wrote: > A pythonX.Y package must have > > 1) a postinst script to byte-compile all previously installed >packages who use dh_purepython > > 2) a prerm script to remove byte-compiled files from all previously >installed packag

pure python modules - Python Policy 2.2.3

2002-01-13 Thread Bastian Kleineidam
Hello Pythoneers, another version of the dh_purepython script is online at http://people.debian.org/~calvin/purepython/. It provides support for Section 2.2.3 of the Python Policy which adresses version-independent Python modules. I would be pleased to hear any comments and/or suggestions from y