Control: severity -1 normal On Sat, Apr 21, 2018 at 01:57:22AM +0200, Fabrizio Pollastri wrote: > <p>Since python-avc 0.8.3-1.1 supports different widget toolkits and > the user is normally interested to only one toolkit among these, I > preferred to set them as "suggested" (the list follows) and not as > dependencies. If there is a better way to define this, any help is > appreciated (I am not an expert Debian packager).<br>
Since the behaviour is intentional, I am lowering the severity of the bug report. Still, I think the behaviour is improvable. Since python-avc really doesn't work at all without any toolkit, having a dependency seems useful to me. For instance, you could put all the suggested toolkits in as alternatives of a single dependency: Suggests: a, b, c, d Depends: a | b | c | d Even after doing so, the module will fail to import though. That has more implications to be considered. For one thing, you cannot use autopkgtest-pkg-python. Then using pydoc fails. This is both unfortunate. An alternative would be to select the toolkit using a function to be called on the imported module. Examples of other libraries where you need to call something before you can use anything are apt_pkg.init() and gbulb.install(). Not sure whether that is "better", but it is something to consider. The other question would be how to exempt python-avc from such tests in order to avoid future bug reports of this kind. Adding it to a whitelist is certainly possible, but also fragile. Helmut
