[all][tc] Dropping lower-constraints testing from all projects

Jeremy Stanley fungi at yuggoth.org
Wed Jan 20 23:03:16 UTC 2021


On 2021-01-20 12:29:44 +0100 (+0100), Radosław Piliszek wrote:
[...]
> I have a related question - do you have a tool to recommend that would
> check whether all modules used directly by the project are in
> requirements.txt already? I.e. that there are no directly-used modules
> that are actually pulled in as indirect dependencies?
> That would improve the proposed approach as well as general
> requirements condition.

I worked on this problem with r1chardj0n3s at an Infra team
get-together circa mid-2014, after Nova unexpectedly broke when a
declared dependency dropped one of its own dependencies which Nova
had at some point started directly importing from without
remembering to also declare it in requirements.txt. I can't take
credit, he did all the real work on it, but we ended up not getting
it added as a common linter because it reused private internals of
pip which later evaporated.

It looks like it was actively adopted and resurrected by a new
author six months ago, so may be worth revisiting:

    https://pypi.org/project/pip-check-reqs/

FWIW, I still think it's fundamentally a good idea.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210120/68b3b840/attachment-0001.sig>


More information about the openstack-discuss mailing list