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

Pants

Untitled

Anybody know how to convince Pip that `pantsbuild-pants==2.24.0` from the constraint file used during Pants plugin resolution (from `[GLOBAL].plugins` option) is the same as `pantsbuild-pants==2.24.0` in the metadata of the particular wheel being installed as a Pants plugin?

The same error occurs if I loosen the wheel to use a version range `pantsbuild-pants&gt;=2.24.0,&lt;2.25`.

Or am I just hitting some silly Pip resolution issue?

[redacted plugin name to `FOO` ]

And this is with forcing the Pex process to use Pip v25.0. (which I had to do manually in the sandbox since Pants was not respecting the `--python-pip-version` option for plugin resolution).

Figured out part of it. Needed to set `--python-repos-find-links` to include <http://wheels.pansbuild.org|wheels.pansbuild.org>