No support for Python packages that rely on manylinux wheels newer than manylinux2014

[svet-b]

Description:

Using sam build (without --use-container) and trying to install a recent version of Polars, such as 1.12.0, fails with "Could not find a version that satisfies the requirement ...". Only Polars versions up to 0.19.12 are listed as available.

This is because Polars stopped shipping wheels based on manylinux2014 (link), on the basis that it's outdated (and essentially EOL).

Meanwhile, at present sam build supports only manylinux up to manylinux2014 (aka manylinux_2_17) wheels, and no versions more recent than that (source). I'm experiencing this on ARM64, but it appears to be true for x86_64 also.

I haven't done a thorough search on how widespread of an issue this is, but there's at least one other similar report here: #674

Given that Python package maintainers are moving away from an outdated version of manylinux, it would be great for this toolchain to also support more recent versions.

I should note that using sam build --use-container does build successfully. But I'd like to avoid that since (a) it adds some weight to the build process, and (b) I'm running the build inside CodePipeline, which is not happy with me trying to spin up a container inside it.

Hopefully it's ok to not add further detail for now as I think the issue I'm describing is self-evident - but happy to attach some detailed logs/reproducers if actually helpful.

[mndeveci]

Thanks for reporting this issue.

If you build it with sam build --use-container, does running sam local invoke and deploying the function works as expected? If so, we need to attach this issue to the one above to make sure AWS Lambda Builders can support the newer manylinux versions that is supported by Lambda.

[svet-b]

Thank you for looking into this. Indeed, after building with --use-container, running sam local invoke works as expected.