ok, I could isolate the issue a bit more. I was already using a recent enough version of pex. It looks like it's only an issue when using a local

--repo

and

--no-pypi

in conjunction with abi3 wheels

# my env:
$ python --version
Python 3.9.7
$ pex --version
2.1.101

# works
$ pex cryptography --platform linux_x86_64-cp-39-cp39 --output-file cryptography.pex

# doesn't work
$ pip wheel cryptography -w wheelhouse
[...]
Saved ./wheelhouse/cryptography-37.0.4-cp36-abi3-manylinux_2_24_x86_64.whl
Saved ./wheelhouse/cffi-1.15.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Saved ./wheelhouse/pycparser-2.21-py2.py3-none-any.whl
$ poetry run pex cryptography --repo wheelhouse --no-pypi --platform linux_x86_64-cp-39-cp39 --output-file cryptography.pex
[...]
ERROR: Could not find a version that satisfies the requirement cryptography (from versions: none)
ERROR: No matching distribution found for cryptography

should I open an issue on gh?

Another thing though, just to check, are you using

--platform

because, for example, you build the PEX on a Mac but want to run it on Linux? If not, you may not need to use

--platform

or

--complete-platform

at all.

Doesn't look too bad, but still a little debugging to do. I'm using the output from

pex3 interpreter inspect

which I passed a python3.8 and python3.9 interpreter as the

--complete-platform

argument (attached the file). I dropped the

--no-pypi

flag, since it seems to complicate things for little gain. The pex builds correctly, but: • I needed to pre-build dependencies locally that only have source releases, since the

pex download

command that is run internally uses

--only-binary :all:

for some reason • the interpreter I'm using to build the pex is 3.9, and it's not including binary wheels for 3.8:

No interpreter compatible with the requested constraints was found:

  A distribution for cffi could not be resolved for /usr/local/bin/python3.8.
  Found 1 distribution for cffi that do not apply:
  1.) The wheel tags for cffi 1.15.1 are cp39-cp39-manylinux_2_17_x86_64, cp39-cp39-manylinux2014_x86_64 which do not match the supported tags of /usr/local/bin/python3.8:
  cp38-cp38-manylinux_2_31_x86_64
  ... 598 more ...

It's working if a 3.9 interpreter is available. I can't test on mac yet, but it would obviously not work yet because I don't know how to include it's info in the supported_platforms.json

In order to use --platform or --complete-platform a pre-requisite is all required distributions must be available as pre-built wheels.

That complete platform file is very surprising. The tags indicate Python 3.9, the markers indicate Python 3.6 - that should not be possible. Can you provide the

pex3 interpreter inspect

command line(s) you use?

If you're targeting, say, 4 platforms, you should run the

pex3 interpreter inspect --python /this/python --markers --tags --indent 2 -o platform1.json

4 times, once on each platform / python you're targeting. Back in Pants you have 4 different

file(...)

targets.

Make sense?

Basically you replace each old abbreviated

--platform

with a

--complete-platform

file, one for one.