dh_python and current python policy doesn't match

[Debian Bug Importer]

Automatically imported from Debian bug report #347758 http://bugs.debian.org/347758

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 12 Jan 2006 14:58:46 +0100
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: dh_python and current python policy doesn't match

Package: python,debhelper
Severity: serious

dh_python currently doesn't honor current python policy (but says so
in the manual page). the version should not yet enter testing until
one of the two is updated.

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Fri, 13 Jan 2006 12:50:21 +0100
From: Josselin Mouette <email address hidden>
To: Matthias Klose <email address hidden>, <email address hidden>
Subject: Re: Bug#347758: dh_python and current python policy doesn't match

Le jeudi 12 janvier 2006 =E0 14:58 +0100, Matthias Klose a =E9crit :
> Package: python,debhelper
> Severity: serious
>=20
> dh_python currently doesn't honor current python policy (but says so
> in the manual page). the version should not yet enter testing until
> one of the two is updated.

I don't think the generated dependencies, as provided, violate the
python policy. The modules are shipped in a directory outside sys.path,
and byte-compiled by a specific application.

Furthermore, this is done in the spirit of some "TODO" sections of the
policy. Of course the policy needs to be updated, but does this really
mandate a RC bug?
--=20
 .''`. Josselin Mouette /\./\
: :' : <email address hidden>
`. `' <email address hidden>
   `- Debian GNU/Linux -- The power of freedom

[Matthias Klose (doko)]

reverted in Debian

[Matthias Klose (doko)]

not ubuntu