[Question] Supported CUDA/Torch/Python combinations

[ko3n1g]

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!

[LyricZhao]

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

[LyricZhao]

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.

[LyricZhao]

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

[ko3n1g]

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

No release, just the tag

[LyricZhao]

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

[ko3n1g]

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).

[ko3n1g]

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

[LyricZhao]

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

[LyricZhao]

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.

[LyricZhao]

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

[ko3n1g]

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.

[LyricZhao]

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.

[LyricZhao]

Does pypi support _ instead of -?

[ko3n1g]

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)