After getting ABI incompatible wheels in my lambda zips, I did the following: 1. Retrieve platform spec from AWS base image 2. Create a target for the platform spec JSON and reference it in

python_awslambda(..., complete_platforms=[":platform"])

However, running

pants package

does not produce a different lambda.zip (I compared checksums) What am I missing?

what happens if you run

./package package

with

--no-local-cache

?

That sounds like https://github.com/pantsbuild/pex/issues/1899 That was identified after a long battle a few weeks ago in Pants slack but no work has been done on it.

Yes, I read most of the thread (109 replies, puh!)

@clever-crayon-70731 are you willing to tackle https://github.com/pantsbuild/pex/issues/1899?

@fast-nail-55400 still the same result, checksums identical

The problem wont go away unless that Pex issue is fixed or else Pants grows an option to not pass

--resolve-local-platforms

when building lambdas. The former is the right fix.

I don't fully understand the problem yet.

Correct.

I'm surprised not more people are facing this issue.

There certainly could be a bystander affect going on.

Is there perhaps a way somewhere to set the target platform to manylinux2014_x86_64? I don't see much in the docs atm.

It already is when you use

runtime

and not a complete platform: + https://github.com/pantsbuild/pants/blob/2aa289a22a46296bff43aa2cbb38bb125dc134c7/src/python/pants/backend/awslambda/python/rules.py#L96 + https://github.com/pantsbuild/pants/blob/2aa289a22a46296bff43aa2cbb38bb125dc134c7/src/python/pants/backend/python/subsystems/setup.py#L403-L413