Joey Hess wrote:
> 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.
Use pyversions -s if pyversions -r fails. pyversions -s will work always as it
lists all supported Python versions. If a package doesn'tlimit itself to Python
versions it works with, it should be built for all supported versions.
>> 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.
Right. Also setup.py *must* work for all supported Python versions (or for the
versions specified in debian/pyversions), otherwise it is broken and will fail
on the next transition. So the best way is to run it with all Python versions as
it will save people from headaches and FTBFS when we migrate to a new Python
version.
>> 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_*.)
They should not break as building for all Python versions is the right way to
go. Modules should also be built with all Python versions to ensure they won't
fail to build at install time when pysupport compiles them. If a package breaks
due to that, it is *not* a bug in dh but a bug in the package.
Cheers,
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
