Re: Python modules for every supported version
On Thu, Jun 17, 2004 at 10:48:02AM +0100, Colin Watson wrote:
> On Thu, Jun 17, 2004 at 09:19:38AM +1000, Robert Collins wrote:
> > On Tue, 2004-06-15 at 18:34, Fabio Tranchitella wrote:
> > > My conclusion is that there are a lot of modules which are not versioned
> > > and are available only for particular versions of python without
> > > motivation. IMHO, can be very useful if every maintaner have to package
> > > versioned python modules. I know people who use python2.1 or python2.2
> > > and I think Debian should think also about them.
> > If debhelper's python support was tweaked to perform the foo required,
> > that would be great.
> The idea of debhelper actually generating entire new binary packages by
> itself terrifies me.
I thought that was pretty much the best option though. For pyrex i did
something ugly like this:
set -e; for version in $(versions); do \
for file in $(files); do \
python$$version setup.py install --root=debian/python$$version-pyrex --no-compile ;\
sed -i "s|#!/usr/bin/python.*|#!/usr/bin/python$$version|" \
mv debian/python$$version-pyrex/usr/bin/$$file \
install -d debian/python$$version-pyrex/usr/share/man/man1/ ;\
install -p -m644 debian/python$$version-$$file.1 \
some more questions:
And about the module location, what goes where exactly:
- usr/lib/site-python ?
Is the second place for modules that do not need byte-compilation ?
There could be a python:Depends to fetch the dependancies of a python module (a
sort of grep ^import *.py) too.
How much problem would it cause to drop python2.1 support?
> Colin Watson [firstname.lastname@example.org]
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com