| 26 Aug 2025 |
 apyh | i'm trying to build master but yaknow, gotta build the world, starting with llvm | 21:23:25 |
| 27 Aug 2025 |
 Kevin Mittman (UTC-8) | There are a fair amount of changes in 13.0, is there already a thread? | 01:45:33 |
 hexa | torch is cached, setuptools upgrades are rarely an issue | 02:11:52 |
| hexa | projects tend to pin it proactively and we tend to unpin it | 02:12:11 |
| apyh | In reply to @hexa:lossy.network
torch is cached, setuptools upgrades are rarely an issue im not super experienced with this - i ask because I'm trying to build torch 2.9 nightly myself, and i can't just bump all versions with the submodule unroll thing, because it fails to build with a newer setuptools. how is torch "cached" such that it doesn't need to build with the setuptools in nixpkgs? | 02:20:20 |
| hexa | https://hydra.nix-community.org/job/nixpkgs/cuda/python3Packages.torch.x86_64-linux | 02:20:54 |
| hexa | but yeah, that version is outdated | 02:21:14 |
| hexa | why newer versions wouldn't work with a newer setuptools but older versions do is beyond me 🙂 | 02:21:31 |
| apyh | yeah no i don't think torch 2.7.1 *should* build with newer setuptools.. | 02:57:01 |
| apyh | oh, i see, 2.7 doesn't have a max version on setuptools (https://github.com/pytorch/pytorch/blob/release/2.7/pyproject.toml) but 2.8 does (https://github.com/pytorch/pytorch/blob/release/2.8/pyproject.toml) | 02:58:29 |
| apyh | ig however it's built in nixpkgs can ignore that constraint since it somehow will still run setup.py | 02:58:57 |
| hexa | they're pinning to a version with distutils exposed, we can just provide distutils 🤷 | 03:25:52 |
