[Build-common-hackers] Bug#424898: Bug#424898: cdbs: don't create debian/pycompat, don't run dh_python

Loïc Minier lool at dooz.org
Thu May 17 17:52:01 UTC 2007

On Thu, May 17, 2007, Bernd Zeimetz wrote:
> Another note: if there is a debian/pycompat file, you must launch
> dh_python after dh_pysupport, but the recommended way is to remove that
> file.

 This is the way the python-support maintainer recommends handling of
 the new policy; it's based on the assumption that "debian/pyversions"
 or the dh_pysupport call themselves are proofs that we're in v2 mode,
 which might be correct, but makes the computation unnecessarily hard.
 For example tools like linda or lintian would have to check for
 implementation specific hints to guess whether the package is following
 Python Policy version 1 or 2 (i.e. check for debian/pyversions for
 python-support based packages and debian/pycompat for anything else).

 I recommend my sponsorees to use such a pycompat file which is still
 the norm for python-central based packages, and is recommended in the
 Python Policy itself anyway.  python-support based packages work fine
 with such a file.

Loïc Minier

More information about the Build-common-hackers mailing list