Issues building a PEX file that can run in different versions of Linux

[foobar-coder]

When I build a pex file in one of the two O.S.s, I get wheel sub-directories that look like this:

.deps/<dep name>-<dep version>-<python impl abbr><python version>-<abi>-manylinux_2_28_x86_64.whl

Whereas in the other OS, with exactly the same BUILD and requirement files I get something like this for the same dependency

.deps/<dep name>-<dep version>-<python impl abbr><python version>-<abi>-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

The PEX file built in the first OS does not run in the second:

pex.environment.ResolveError: A distribution for <dep name> could not be resolved in this environment.
Found 1 distribution for <dep name> that do not apply:
1.) The wheel tags for <dep name> <dep version> are
 <python impl abbr><python version>-<abi>-manylinux_2_28_x86_64
 which do not match the supported tags of DistributionTarget(interpreter=PythonInteentity(...

I tried using the attribute pex_binary.platforms but I cannot find the right strings to use.

Can pants build a PEX file including dependencies for both manylinux_2_17_x86_64 and manylinux_2_28_x86_64?

If so, how?

---

P.S. I posted this initially under issues, but it seems that discussions is a better place

[cburroughs]

You you been able to take a stab with complete_platforms? https://www.pantsbuild.org/2.19/docs/python/overview/pex#setting-the-target-platforms-for-a-pex

[foobar-coder]

You you been able to take a stab with complete_platforms?

Thanks, I can try.

But I am using an old version of pants that does not support complete_platforms

What's the fist version of pants that added support for complete_platforms?

[foobar-coder]

What's the fist version of pants that added support for complete_platforms?

It seems to be 2.10.x

[foobar-coder]

Anyway, I tried the instructions provided

With the JSON generated, I was able to build in platform 2.28 a pex file that worked in both 2.28 and 2.17 using pants 2.18.x and complete_platforms.

pex3 interpreter inspect --markers --tags -i 2 --python 'python3.9' >cp39-cp39-manylinux_2_17_x86_64.json

...
file(
    name="manylinux_2_17_x86_64",
    source="cp39-cp39-manylinux_2_17_x86_64.json"
)

pex_binary(
    name='some_pex',
...
    output_path='some_pex',
    complete_platforms=[":manylinux_2_17_x86_64"]
)
...

I could make it work only when including files for 2.17, though, which seems to be good enough for my case. So, not truly "multi-platform" I suppose, but works for me in this instance.