[PR #217] [MERGED] Ko3n1g/chore/rename to deepgemm #293

Closed
opened 2026-10-26 21:15:55 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/217
Author: @ko3n1g
Created: 10/15/2025
Status: ✅ Merged
Merged: 10/15/2025
Merged by: @LyricZhao

Base: main ← Head: ko3n1g/chore/rename-to-deepgemm


📝 Commits (2)

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 .github/workflows/publish.yml (+1 -1)
📝 setup.py (+1 -1)

📄 Description

Since deep_gemm is already taken on PyPI, we need to change our project name to deepgemm.


Background: By default, project name == package name. I.e. pip install numpy; import numpy.

However, some projects diverge: pip install pillow; import PIL


SInce deep-gemm is taken, we will now change our strategy from pip install deep-gemm; import deep_gemm to pip install deepgemm; import deep_demm

The only caveat is that if users believe they need to do pip install deep-gemm they will install the other package not ours. However, since the other deep-gemm package has been on PyPI for long this was always the case.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/DeepGEMM/pull/217 **Author:** [@ko3n1g](https://github.com/ko3n1g) **Created:** 10/15/2025 **Status:** ✅ Merged **Merged:** 10/15/2025 **Merged by:** [@LyricZhao](https://github.com/LyricZhao) **Base:** `main` ← **Head:** `ko3n1g/chore/rename-to-deepgemm` --- ### 📝 Commits (2) - [`d954296`](https://github.com/deepseek-ai/DeepGEMM/commit/d9542968f3ec83ec4134dac07a8a4d57dda08c50) py3.8 - [`192f5f1`](https://github.com/deepseek-ai/DeepGEMM/commit/192f5f176fb9ee8b9e7c229d286e78eec9c8f155) chore: Rename from `deep_geem` to `deepgemm` ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/publish.yml` (+1 -1) 📝 `setup.py` (+1 -1) </details> ### 📄 Description Since `deep_gemm` is already taken on PyPI, we need to change our project name to `deepgemm`. --- Background: By default, project name == package name. I.e. `pip install numpy; import numpy`. However, some projects diverge: `pip install pillow; import PIL` --- SInce deep-gemm is taken, we will now change our strategy from `pip install deep-gemm; import deep_gemm` to `pip install deepgemm; import deep_demm` The only caveat is that if users believe they need to do `pip install deep-gemm` they will install the other package not ours. However, since the other deep-gemm package has been on PyPI for long this was always the case. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 21:15:55 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
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#293
No description provided.