FR: wheels that support optional modules
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python, pytorch
- Domain
- build-system, tooling
Research direction
No files or tests are named. Start by tracing the wheel build and package metadata behind torchcomms, then check how pip extras could select nccl or rccl backends. Done means the optional installation variants produce wheels that omit unrequested heavy modules while retaining the requested backend.
Written by the indexing model from the issue text.
Description
Hi developers,
torchcomms claims to be a light-weight library, but ncclx seems to be heavy:
14M /lib/python3.14/site-packages/torchcomms/_comms.cpython-314-x86_64-linux-gnu.so
12M /lib/python3.14/site-packages/torchcomms/_comms_gloo.cpython-314-x86_64-linux-gnu.so
15M /lib/python3.14/site-packages/torchcomms/_comms_nccl.cpython-314-x86_64-linux-gnu.so
654M /lib/python3.14/site-packages/torchcomms/_comms_ncclx.cpython-314-x86_64-linux-gnu.so
12K /lib/python3.14/site-packages/torchcomms/_comms.pyi
8.0K /lib/python3.14/site-packages/torchcomms/device_mesh.py
4.0K /lib/python3.14/site-packages/torchcomms/__init__.py
11M /lib/python3.14/site-packages/torchcomms/libtorchcomms.so
32K /lib/python3.14/site-packages/torchcomms/objcol.py
40K /lib/python3.14/site-packages/torchcomms/__pycache__
376K /lib/python3.14/site-packages/torchcomms/tests
I wonder if we can just do pip install torchcomms[nccl] to specify the backend such that ncclx can be excluded optionally, and similarly pip install torchcomms[rccl].
Thanks!
- Dominant language
- C++
- Stars
- 396
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from meta-pytorch/torchcomms
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
meta-pytorch/torchcomms#3311 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
meta-pytorch/torchcomms#4146 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
meta-pytorch/torchcomms#4073 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
meta-pytorch/torchcomms#3169 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
meta-pytorch/torchcomms#3168 ·
All issues in meta-pytorch/torchcomms
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·