[GH-ISSUE #212] [Question] Supported CUDA/Torch/Python combinations #122

New issue

Open

opened 2026-10-26 21:13:03 +00:00 by bsakaguchi · 21 comments

bsakaguchi commented 2026-10-26 21:13:03 +00:00

Owner

Copy link

Originally created by @ko3n1g on GitHub (Oct 11, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/212

Originally assigned to: @LyricZhao on GitHub.

Hey @LyricZhao,

in my fork I tried to dry-run the publish workflow and found that some wheels cannot be build. Could you have a brief look and check if we need to exclude i.e. old cuda or old python versions?

I'll submit a new PR soon to finalize the wheel build

Run: https://github.com/ko3n1g/DeepGEMM/actions/runs/18435420460

Thx!

Originally created by @ko3n1g on GitHub (Oct 11, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/212 Originally assigned to: @LyricZhao on GitHub. Hey @LyricZhao, in my fork I tried to dry-run the publish workflow and found that some wheels cannot be build. Could you have a brief look and check if we need to exclude i.e. old cuda or old python versions? I'll submit a new PR soon to finalize the wheel build Run: https://github.com/ko3n1g/DeepGEMM/actions/runs/18435420460 Thx!

bsakaguchi commented 2026-10-26 21:13:04 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 13, 2025):

Thanks for the fixes, CUDA {12, 13} x Python {3.8, 3.9, 3.10, 3.11, 3.12, 3.13} are enough.

<!-- gh-comment-id:3395597797 --> @LyricZhao commented on GitHub (Oct 13, 2025): Thanks for the fixes, CUDA {12, 13} x Python {3.8, 3.9, 3.10, 3.11, 3.12, 3.13} are enough.

bsakaguchi commented 2026-10-26 21:13:05 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 13, 2025):

In https://github.com/deepseek-ai/DeepGEMM/pull/214/files, I saw you remove the Python 3.8 support? Our cluster has some Python 3.8 environment, which means we still need it.

<!-- gh-comment-id:3395598765 --> @LyricZhao commented on GitHub (Oct 13, 2025): In https://github.com/deepseek-ai/DeepGEMM/pull/214/files, I saw you remove the Python 3.8 support? Our cluster has some Python 3.8 environment, which means we still need it.

bsakaguchi commented 2026-10-26 21:13:05 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 13, 2025):

Another way to solve the Python issue, is to use a Python ABI framework that supports any Python :)

<!-- gh-comment-id:3395599948 --> @LyricZhao commented on GitHub (Oct 13, 2025): Another way to solve the Python issue, is to use a Python ABI framework that supports any Python :)

bsakaguchi commented 2026-10-26 21:13:05 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 14, 2025):

@LyricZhao could you create and push a new tag to main?:)

No release, just the tag

<!-- gh-comment-id:3400129885 --> @ko3n1g commented on GitHub (Oct 14, 2025): @LyricZhao could you create and push a new tag to main?:) No release, just the tag

bsakaguchi commented 2026-10-26 21:13:06 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 14, 2025):

Pushed, thx again! https://github.com/deepseek-ai/DeepGEMM/releases/tag/v2.1.1

<!-- gh-comment-id:3400574900 --> @LyricZhao commented on GitHub (Oct 14, 2025): Pushed, thx again! https://github.com/deepseek-ai/DeepGEMM/releases/tag/v2.1.1

bsakaguchi commented 2026-10-26 21:13:06 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 14, 2025):

Are you the owner of https://pypi.org/project/deep-gemm/? If so, can you add ko3n1g as maintainer to it?

---

Edit: In case you are not the owner, we can choose the project name deepgemm instead of deep_gemm. Note that the package name will be untouched (it will still be: deep_gemm).
In short: Project-name and Package-name are often the same, but pip doesn't enforce it (take PIL and pillow as an example).

<!-- gh-comment-id:3400968168 --> @ko3n1g commented on GitHub (Oct 14, 2025): Are you the owner of https://pypi.org/project/deep-gemm/? If so, can you add `ko3n1g` as maintainer to it? --- Edit: In case you are not the owner, we can choose the project name `deepgemm` instead of `deep_gemm`. Note that the package name will be untouched (it will still be: `deep_gemm`). In short: Project-name and Package-name are often the same, but pip doesn't enforce it (take `PIL` and `pillow` as an example).

bsakaguchi commented 2026-10-26 21:13:07 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

In case this notification got lost in transit, @LyricZhao :)

<!-- gh-comment-id:3405146440 --> @ko3n1g commented on GitHub (Oct 15, 2025): In case this notification got lost in transit, @LyricZhao :)

bsakaguchi commented 2026-10-26 21:13:07 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

Oh, sorry. Creating now (I am not the owner)

<!-- gh-comment-id:3405160736 --> @LyricZhao commented on GitHub (Oct 15, 2025): Oh, sorry. Creating now (I am not the owner)

bsakaguchi commented 2026-10-26 21:13:07 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

Sorry, can you create the project for me? We have lots of internal stuffs going, I am not familar with PyPi packing and distribution, and my time is limited.

<!-- gh-comment-id:3405199932 --> @LyricZhao commented on GitHub (Oct 15, 2025): Sorry, can you create the project for me? We have lots of internal stuffs going, I am not familar with PyPi packing and distribution, and my time is limited.

bsakaguchi commented 2026-10-26 21:13:08 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

I've created the account, but seems more procedures to distribute.

<!-- gh-comment-id:3405201406 --> @LyricZhao commented on GitHub (Oct 15, 2025): I've created the account, but seems more procedures to distribute.

bsakaguchi commented 2026-10-26 21:13:08 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

No worries happy to help. But are you fine we're diverging from the name deep-gemm as this is already taken by someone else? We would choose deepgemm instead.

<!-- gh-comment-id:3405204241 --> @ko3n1g commented on GitHub (Oct 15, 2025): No worries happy to help. But are you fine we're diverging from the name `deep-gemm` as this is already taken by someone else? We would choose `deepgemm` instead.

bsakaguchi commented 2026-10-26 21:13:08 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

I think deep_gemm is better? As our training/inference framework is using import deep_gemm. Changing into deepgemm will introduce so many compatibility issues.

<!-- gh-comment-id:3405347560 --> @LyricZhao commented on GitHub (Oct 15, 2025): I think `deep_gemm` is better? As our training/inference framework is using `import deep_gemm`. Changing into `deepgemm` will introduce so many compatibility issues.

bsakaguchi commented 2026-10-26 21:13:09 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

Does pypi support _ instead of -?

<!-- gh-comment-id:3405349145 --> @LyricZhao commented on GitHub (Oct 15, 2025): Does pypi support `_` instead of `-`?

bsakaguchi commented 2026-10-26 21:13:09 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

this is not about the import-name but about the pip-install command.

It will always stay import deep_gemm

but we have to go with pip install deepgemm instead of pip install deep-gemm (since the latter is already taken)

<!-- gh-comment-id:3405379890 --> @ko3n1g commented on GitHub (Oct 15, 2025): this is not about the import-name but about the pip-install command. It will always stay `import deep_gemm` but we have to go with `pip install deepgemm` instead of `pip install deep-gemm` (since the latter is already taken)

bsakaguchi commented 2026-10-26 21:13:09 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

How about pip install deep_gemm? Consistent with importing names.

<!-- gh-comment-id:3405530472 --> @LyricZhao commented on GitHub (Oct 15, 2025): How about `pip install deep_gemm`? Consistent with importing names.

bsakaguchi commented 2026-10-26 21:13:10 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

Also taken, PyPI auto-translates _ to -.

<!-- gh-comment-id:3405534518 --> @ko3n1g commented on GitHub (Oct 15, 2025): Also taken, PyPI auto-translates `_` to `-`.

bsakaguchi commented 2026-10-26 21:13:10 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

Ok, then deepgemm is fine for me :)

<!-- gh-comment-id:3405580594 --> @LyricZhao commented on GitHub (Oct 15, 2025): Ok, then `deepgemm` is fine for me :)

bsakaguchi commented 2026-10-26 21:13:10 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

Here's the required PR: https://github.com/deepseek-ai/DeepGEMM/pull/217

<!-- gh-comment-id:3405587928 --> @ko3n1g commented on GitHub (Oct 15, 2025): Here's the required PR: https://github.com/deepseek-ai/DeepGEMM/pull/217

bsakaguchi commented 2026-10-26 21:13:11 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

Thanks a lot for taking your time to discuss this with me! We're almost done:)

<!-- gh-comment-id:3405589892 --> @ko3n1g commented on GitHub (Oct 15, 2025): Thanks a lot for taking your time to discuss this with me! We're almost done:)

bsakaguchi commented 2026-10-26 21:13:11 +00:00

Author

Owner

Copy link

@LyricZhao commented on GitHub (Oct 15, 2025):

Thanks! Already merged.

<!-- gh-comment-id:3405647012 --> @LyricZhao commented on GitHub (Oct 15, 2025): Thanks! Already merged.

bsakaguchi commented 2026-10-26 21:13:11 +00:00

Author

Owner

Copy link

@ko3n1g commented on GitHub (Oct 15, 2025):

I'll create a new tag now (hope its fine)

<!-- gh-comment-id:3405739713 --> @ko3n1g commented on GitHub (Oct 15, 2025): I'll create a new tag now (hope its fine)

bsakaguchi referenced this issue 2026-10-26 21:15:24 +00:00

[PR #122] [MERGED] [add] fix smem_barrier size in wgrad way #253

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

public-sync-20261014

0930-release

nv_dev

fix-mega-moe-fence

public-release-2609

public-release-2607

public-release-2606

mega-update

public-release-260416

ko3n1g/ci/build-wheels

nv_dev_f8e8fb5

nv_dev_950d31a

nv_dev_67fc648

nv_dev_c491439

nv_dev_4ff3f54

v2.1.1.post3

v2.1.1.post2

v2.1.1.post1

v2.1.1

v2.1.0

Labels

Clear labels   

pull-request

Mirrored from GitHub Pull Request

No labels

pull-request

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

deepseek-ai/DeepGEMM#122

No description provided.