Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

The error messages for packages that don't have a binary package and you specified them in `resolves_to_only_binary` are... not great.

``` The conflict is caused by:
     The user requested Appium-Python-Client==1.2.0
     The user requested (constraint) appium-python-client>=1.2.0
 
 To fix this you could try to:
 1. loosen the range of package versions you've specified
 2. remove package versions to allow pip attempt to solve the dependency conflict```
I get this is a pip issue, but still.

I'm not sure if pants can do anything here, but in general these issues are very hard to track down. Here it was obvious, since I knew what I changed, but very often it's hard to figure out where these requirements/constraints come from.

I guess, hm, it'd be nice to get information about constraints and requirements about a package. We have one big requirements file for the repo, but several apps have their own requirements. I guess it's easier to tell now with lockfiles, but you still need to track down what exactly caused these requirements/constraints to be generated.