Url based constraints

[thenewguy]

I've been issued a depreciation warning and found #8210

That issue is locked for commenting. We use constraints that point to tarball urls like https://github.com/some/repo/archive/bugfix-issue-foo.tar.gz#egg=somepackage

This conceptually is a constraint as it is just a bugfix of a public release that we do not control the upstream release process. This lets us point towards the fix until upstream releases a fix. We have many common packages and use a global constraint file to facilitate these fixes globally. Requiring a new requirement is unwarranted because it is typically temporary until upstream is able to act.

Removing this feature is very unfortunate. It saves a lot of error and duplication of work.

[uranusjr]

Merging into #8253. The feature will continue to exist, but likely offered in another way. #8210 was closed because it was decided that “nameless” constraints are not going to be allowed (although it does contain much discussion on named URL requirements). Feel free to contribute to the discussion, since we need to come to a conclusion before the resolver rollout is done.

Also, thanks for reaching out to say this is a feature used in the real-world! The biggest concern we had discussing this topic was the use case seems too hypothetical. It would greatly affect the decision process if we have concrete use cases to the feature at hand.