On Sat, 7 Jan 2017 18:26:58 -0800 Afif Elghraoui <a...@debian.org> wrote: > > > On السبت 7 كانون الثاني 2017 15:17, Sandro Tosi wrote: > > On Sat, Jan 7, 2017 at 5:34 PM, Afif Elghraoui <a...@debian.org> wrote: > >> I hope what I've said now convinces you > > > > > > sadly you didnt > > > > What is it that doesn't make sense to you? Is it that you don't agree > that the current situation violates policy or that you just don't want > to change it? > > The specific case in which I discovered this problem is that installing > pbhoney gets all of networkx's unnecessary recommends. If you do > no-install-recommends to avoid the unnecessary recommends, you don't get > pbhoney's legitimate recommends of pbdagcon and unnecessarily use the > inferior built-in fallback implementation. > > If I made pbdagcon a hard dependency, then you would not be able to > install pbhoney in a situation where pbdagcon isn't available without > making a dummy package using equivs. > > What functionality of *networkx* is affected when its recommends are not > installed? If the answer is nothing, which it seems to be, then they > definitely don't belong in recommends.
There is no concept of Recommends in setuptools metadata: either something is listed in `install_requires` then the relationship is Depends, or in extras_require then it is Suggests. Period. Ghis
