On Sun, 2020-05-10 at 12:39 -0400, Doug Hellmann wrote:The PyPA team is working on a new resolver for pip. As part of that work, they have had some questions about the way
OpenStack uses the constraints feature. They’ve been great about taking input, and prometheanfire has been doing some
testing to ensure the new work doesn’t break compatibility [1] (thanks Matthew!).
There is a new question from the pip maintainers about whether constraints need to support “nameless” entries (by
referring to a URL in a constraints file instead of using package names) [2]. I don’t see anything in the upper-
constraints.txt that looks like a URL, but I don’t know how teams might be configuring their lower-constraints.txt or
whether we do anything in devstack to munge the constraints list to point to local packages as part of LIBS_FROM_GIT
handling.
Is anyone aware of any uses of URLs in constraints files anywhere within OpenStack?
yes we sometimes have urls to git repos.they are not in constraits files but the are in test-requiremente or requirements.txt
OK, the question is specifically about whether unnamed dependencies listed in *constraints* are somehow expected to work. Having URLs in requirements lists isn’t an issue.
jrosser pointed out on IRC that openstack-ansible uses URLs with egg= so I’ve suggested describing that upstream in case it’s relevant.
It sounds like this might be another case to describe on that pypa GitHub issue.