On Fri, Apr 10, 2009 at 03:50:05PM -0400, Joey Hess wrote: > Julian Andres Klode wrote: > > Change the behaviour of the dh_auto_* scripts to get the requested > > Python versions from `pyversions -r` and build for all of them, instead > > of just the current Python version. > > Can we be sure that > > * pyversions -r will list some python versions for every package > with a setup.py file? It won't if the control file field and > pyversions file are missing. Looks to me like dh_pysupport does not > require that version info, so there is no guarantee it is present. pyversions -r lists all supported versions if the field in debian/control and debian/pyversions are both missing. If debian/pyversions is empty it would fail, but debian/pyversions should never be empty. At least this is what I saw in my local testing. > So the code probably needs to fall back to using just python if > pyversions lists nothing. > * running setup.py multiple times with different versions of python > will always work, and not break in some way? If they use the standard functionality provided by python distutils, python-distutils-extra or python-setuptools it should work. As far as I know cdbs also builds for all requested python versions, so it should be safe to adapt this way of building. I CCed debian-python@lists.debian.org, so we can get some feedback from there. -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juliank@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/
Attachment:
signature.asc
Description: Digital signature