Python Policy suggests dependencies that prevent installation

[Loïc Minier <lool+debian@via.ecp.fr>]

        Hi,

 Python Policy 3.2 states:

 3.2 Programs Using a Particular Python Version

 """A program which requires a specific version of Python must begin with
 #!/usr/bin/pythonX.Y (or #!/usr/bin/env pythonX.Y). It must also
 specify a dependency on pythonX.Y and on any pythonX.Y-foo package
 providing necessary modules. It should not depend on any python-foo
 package, unless it requires a specific version of the package (since
 virtual packages cannot be versioned). If this is the case, it should
 depend on both the virtual package and the main package (e.g. Depends:
 python2.4-foo, python-foo (>= 1.0))."""


 Consider gnome-osd which depended on python2.4-pyorbit-omg before
 pyorbit was transitioned.  Now pyorbit only ships python-pyorbit-omg
 which Provides python2.4-pyorbit-omg, but users with gnome-osd
 installed -- and hence python2.4-pyorbit-omg as a real package
 installed -- won't get python-pyorbit-omg.

 Shouldn't such packages Depend on "python-pyorbit-omg,
 python2.4-pyorbit-omg", even if they don't need a particular version of
 python-pyorbit-omg (contrarily to what 3.2 §2 requests)?

   Bye,
-- 
Loïc Minier <lool@dooz.org>