[ethanwee1]

Problem

Triton 3.8 builds on Python 3.15, but its wheel metadata rejects installation. Its annotated-default AST construction is also invalid on Python 3.15.

Changes

• Allow Python 3.15 in wheel metadata.
• Backport [Frontend] Pass simple flag when constructing AnnAssign nodes triton-lang/triton#10986 and strengthen its regression test.

Dependencies

• TheRock release enablement: ci(pytorch): add Python 3.15 release builds TheRock#8394.
• Stable PyTorch pins: [release/2.12] Update Python 3.15 dependency pins pytorch#3676, [release/2.13] Update Triton for Python 3.15 pytorch#3678, and [release/2.14] Update Triton for Python 3.15 pytorch#3677.
• PyTorch 2.12 build frontend and CK support: fix(pytorch): upgrade pypa/build for Python 3.15 argparse TheRock#8428 and [release/2.12] Support Python 3.15 module loading composable_kernel#3774.
• Nightly counterpart: Support Python 3.15 and build 3.15t wheels triton-lang/triton#11433.

Validation

• Targeted pre-commit, Python compile checks, and the metadata-ceiling assertion passed.
• 2.12 proofs: Linux passed, Windows passed.
• 2.13 proofs: Linux passed, Windows passed.
• 2.14 proofs: Linux passed, Windows passed.
• Remaining ROCm/triton CI failures are unrelated runner/toolchain failures; the PR is approved.

Tracked in AIPYTORCH-1241.

New contributor declaration

• I am not making a trivial change, such as fixing a typo in a comment.
• I have written a PR description following these rules.
• I have added tests.
• I have not added any lit tests.

[ethanwee1]

Dependent pin updates are open for ROCm/pytorch release/2.12 (triton-lang#3676), release/2.13 (triton-lang#3678), and release/2.14 (triton-lang#3677).

[jithunnair-amd]

@zhanglx13 Can you help assess if these failures are legit? We need to bump 3.8 branch to support python3.15.

[ethanwee1]

I confirmed with @zhanglx13 and we do not have to pass CI to merge the PR

[jithunnair-amd]

I don't seem to have merge powers here