Bug: PythonUvBuilder does not target Lambda manylinux compatibility

未关闭
  • 哪里不对？
#955 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

@vinsymoyya 已经在做这个了。

开始于 2026年11月6日。

  • #956 来自 @vinsymoyya —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
70/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by reading the PythonUvBuilder and UvRunner code that constructs the uv pip install platform target; the issue identifies the python_uv workflow and gives a local wheel reproduction. Check how Python runtime version and architecture map to Lambda's AL2 and AL2023 glibc compatibility, then run the reproduction for both architectures and runtime groups. Done means the Python 3.12+ case selects manylinux_2_34, the Python 3.8–3.11 case targets AL2 compatibility, and the incompatible wheel is rejected.

由索引模型根据 Issue 内容生成。

描述

Description

PythonUvBuilder passes x86_64-unknown-linux-gnu or aarch64-unknown-linux-gnu to uv pip install for every Python runtime. These generic targets do not encode Lambda's runtime-specific manylinux compatibility.

On Windows with uv 0.11.26, I reproduced both:

  • python3.11: given wheels tagged manylinux_2_17 and manylinux_2_28, the builder selects the latter. Lambda's AL2 runtime has glibc 2.26, so a wheel requiring 2.28 is incompatible.
  • python3.12: given wheels tagged manylinux_2_34 and manylinux_2_35, the builder fails to find a compatible wheel, even though Lambda's AL2023 runtime supports glibc 2.34. Using x86_64-manylinux_2_34 selects the correct wheel.

The same results reproduce for arm64. The fixtures below test wheel selection using valid wheel metadata; they do not require compiling or loading a native extension.

Steps to reproduce

Run with aws-lambda-builders 1.68.0 and uv installed. This example exercises the Python 3.12 failure using local wheels only:

import os
from pathlib import Path
from tempfile import TemporaryDirectory
from zipfile import ZipFile
from aws_lambda_builders.workflows.python_uv.packager import UvRunner

with TemporaryDirectory() as directory:
    root = Path(directory)
    wheels = root / "wheels"
    wheels.mkdir()
    for minor in (34, 35):
        tag = f"py3-none-manylinux_2_{minor}_x86_64"
        with ZipFile(wheels / f"platform_demo-1.0.0-{tag}.whl", "w") as wheel:
            wheel.writestr("platform_demo.py", f"GLIBC_MINOR = {minor}\n")
            wheel.writestr("platform_demo-1.0.0.dist-info/METADATA",
                          "Metadata-Version: 2.1\nName: platform-demo\nVersion: 1.0.0\n")
            wheel.writestr("platform_demo-1.0.0.dist-info/WHEEL",
                          f"Wheel-Version: 1.0\nRoot-Is-Purelib: false\nTag: {tag}\n")
            wheel.writestr("platform_demo-1.0.0.dist-info/RECORD", "")
    manifest = root / "requirements.txt"
    manifest.write_text("platform-demo==1.0.0\n", encoding="utf-8")
    os.environ.update(UV_NO_INDEX="1", UV_OFFLINE="1", UV_FIND_LINKS=wheels.as_uri())
    UvRunner().install_requirements(
        str(manifest), str(root / "artifacts"),
        python_version="3.12", platform="linux", architecture="x86_64",
    )
Observed result

UvInstallationError: ... platform-demo==1.0.0 has no wheels with a matching platform tag (e.g., manylinux_2_28_x86_64)

Expected result

Select the glibc 2.34 wheel for Python 3.12+, reject the 2.35 wheel, and use AL2-compatible targeting for Python 3.8-3.11. The selection should follow the Lambda runtime and architecture rather than generic GNU/Linux defaults.

AWS documents the glibc 2.26 / 2.34 runtime boundary. UV supports explicit manylinux targets.

Environment and related work
  • Windows, Python 3.13.3, uv 0.11.26
  • aws-lambda-builders 1.68.0, upstream commit e3e14536501e38b0d6d8db582ddec6d0e0bd6f8a
  • Reproduced through LambdaBuilder.build() for both architectures and both experimental-flag settings.
  • #700, #752, and #762 concern python_pip; this report concerns the separate python_uv command construction. I checked the open/closed issue and PR history for an existing UV fix.
主要语言
Python
星标
381
派生
161
平均合并
5 天 14 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aws/aws-lambda-builders 的其他 Issue

查看 aws/aws-lambda-builders 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。