Julian Andres Klode wrote: > 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. You're right. > 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. I'm mostly worried about breaking any existing packages that use dh or dh_auto_*, and somehow contain something that breaks if it's changed to start building multiple times for multiple python versions. (There are probably few if any such packages, but I do have to worry about backward compatability when I change dh_auto_*.) -- see shy jo
Attachment:
signature.asc
Description: Digital signature