🐛 Describe the bug
While testing I noticed that wheel constraint does not work :
Requires-Dist: pytorch-triton==3.2.0+git35c6c7c6; platform_system == "Linux" and platform_machine == "x86_64" and python_version != "3.13t"
Workflow:
https://github.com/pytorch/pytorch/actions/runs/12427438642/job/34700799523#step:15:533
Looks like this is currently not supported :
Related Doc: https://packaging.python.org/en/latest/specifications/dependency-specifiers/
Discussion: https://discuss.python.org/t/environment-marker-for-free-threading/60007/4
Hence I propose following:
For release and nightly Remove triton constrain from 3.13t wheels METADATA:
Requires-Dist: pytorch-triton==3.2.0+git35c6c7c6; platform_system == "Linux" and platform_machine == "x86_64" and python_version != "3.13t"
When publishing these wheels to pypi, publish them after linux 3.9-3.13 wheels are uploaded as separate step to avoid possible issues with poetry.
Versions
2.6.0
cc @seemethere @malfet @osalpekar
🐛 Describe the bug
While testing I noticed that wheel constraint does not work :
Workflow:
https://github.com/pytorch/pytorch/actions/runs/12427438642/job/34700799523#step:15:533
Looks like this is currently not supported :
Related Doc: https://packaging.python.org/en/latest/specifications/dependency-specifiers/
Discussion: https://discuss.python.org/t/environment-marker-for-free-threading/60007/4
Hence I propose following:
For release and nightly Remove triton constrain from 3.13t wheels METADATA:
When publishing these wheels to pypi, publish them after linux 3.9-3.13 wheels are uploaded as separate step to avoid possible issues with poetry.
Versions
2.6.0
cc @seemethere @malfet @osalpekar