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? Doug [1] https://review.opendev.org/#/c/726186/ [2] https://github.com/pypa/pip/issues/8210