[TRTLLM-14709][infra] Require packaging>=24.2 for FlashInfer source builds - #17075
Conversation
…uilds FlashInfer source installs with --no-build-isolation fail during metadata preparation when the environment ships packaging<24.2 (e.g. packaging==24.0): setuptools' license-expression validation (_finalize_license_expression) raises ImportError, since it requires packaging>=24.2. TensorRT-LLM has no direct packaging requirement today, so adding the floor to requirements.txt is conflict-free and ensures environments built from TRT-LLM requirements can build FlashInfer from source. Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
|
/bot run |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds ChangesFlashInfer build dependency
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #62830 [ run ] triggered by Bot. Commit: |
b5d7a4f to
381b6d2
Compare
…rkaround from Kimi K3 docs Mirrors main PR NVIDIA#17075: FlashInfer source builds with --no-build-isolation need packaging>=24.2 for setuptools license-expression validation, so declare it in requirements.txt and remove the manual 'pip install -U packaging' step from the Kimi K3 README and deployment guide. Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
|
Author notes (preserving context from the original PR description):
|
|
/bot run |
|
PR_Github #62873 [ run ] triggered by Bot. Commit: |
|
PR_Github #62830 [ run ] completed with state |
…rkaround from Kimi K3 docs Mirrors main PR NVIDIA#17075: FlashInfer source builds with --no-build-isolation need packaging>=24.2 for setuptools license-expression validation, so declare it in requirements.txt and remove the manual 'pip install -U packaging' step from the Kimi K3 README and deployment guide. Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
|
PR_Github #62873 [ run ] completed with state
|
|
/bot run |
|
PR_Github #62921 [ run ] triggered by Bot. Commit: |
|
PR_Github #62921 [ run ] completed with state
|
|
/bot skip --comment "only sets requirements.txt for flashinfer builds, no functional changes" |
|
PR_Github #63024 [ skip ] triggered by Bot. Commit: |
|
PR_Github #63024 [ skip ] completed with state |
|
PR_Github #63042 [ skip ] triggered by Bot. Commit: |
|
PR_Github #63042 [ skip ] completed with state |
|
/bot skip --comment "only sets requirements.txt for flashinfer builds, no functional changes" |
|
PR_Github #63058 [ skip ] triggered by Bot. Commit: |
|
PR_Github #63058 [ skip ] completed with state |
Dev Engineer Review
packaging>=24.2torequirements.txtfor FlashInfer source builds using--no-build-isolation.QA Engineer Review
No test changes.
Description
FlashInfer source installs with
--no-build-isolationhard-fail during metadata preparation on environments that shippackaging<24.2(e.g. NGC PyTorch containers withpackaging==24.0): setuptools' license-expression validation (_finalize_license_expression) raisesImportError, because it requirespackaging>=24.2.This was hit during Kimi K3 bring-up, where the documented flow installs a pinned FlashInfer revision from source with
--no-build-isolation. TensorRT-LLM has no directpackagingrequirement today, so adding apackaging>=24.2floor torequirements.txtis conflict-free and ensures environments built from TRT-LLM requirements can build FlashInfer from source.This is Wave A of the feat/kimi_k3 → main staging plan.
Test Coverage
Metadata-only change; validated locally:
requirements*/constraints*/*.tomlfiles: no otherpackagingpin exists in the repo, so the floor is conflict-free.pip install --dry-run "packaging>=24.2" "setuptools<80"resolves cleanly (packaging 26.2 + setuptools 79.0.1).setup.py'sparse_requirements()against the editedrequirements.txt: all 90 dependency entries parse as valid requirements, withpackaging>=24.2picked up.packaging==24.0container env, applying the floor was previously verified to make the pinned FlashInfer source build succeed (2026-07-27).PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.