deepspeedai / deepspeedai/DeepSpeed
[REQUEST] Publish your Windows Wheels build workflow
@loadams is already working on this.
Since Feb 20, 2025.
- Dominant language
- Python
- Stars
- 43.1k
- Forks
- 5k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 112
Description
I am unable to use DeepSpeed because my project requires pytorch 2.5.1 and cudnn 9, and the provided wheels are VERY specific (Python 3.11 and Torch 2.3: https://pypi.org/project/deepspeed/0.16.3/#files)
Since the wheels do not specify the torch requirement, the error can only be seen when trying to use deepspeed, rather than when installing.
I would like to request that you publish the recipe (preferably using a github workflow file) so we can experiment and potentially build ourselves, starting with a working setup.
Specifically I would like to see a workflow with a matrix of Python 3.11 and 3.12, and Torch 2.3, 2.5 (there are other newer versions but those are the one I use that most packages support).
There are multiple issues that seem to report specific issues related to Windows; this issue is not about solving any given Windows install limitation, but to release the working recipe you used in the 16.3 release in a github workflow matrix format.
I tried again to build from source and failed. Therefore, even if you do not want to invest time in supporting additional, more recent versions of torch and python, it would be appreciated to have access to the build recipe.
Related issues, :
- https://github.com/deepspeedai/DeepSpeed/issues/6673
- https://github.com/deepspeedai/DeepSpeed/issues/7043
- https://github.com/deepspeedai/DeepSpeed/issues/6981
- https://github.com/deepspeedai/DeepSpeed/issues/6865
- https://github.com/deepspeedai/DeepSpeed/issues/6871
- https://github.com/deepspeedai/DeepSpeed/issues/6625
- https://github.com/deepspeedai/DeepSpeed/issues/6465
- https://github.com/deepspeedai/DeepSpeed/issues/4729
That would probably help reduce the amount of tickets, or make tickets more specific at least.
Thanks for the amazing library!
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.
Assessment
This issue has not been assessed yet.