mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[PR #217] [MERGED] Ko3n1g/chore/rename to deepgemm #293
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#293
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 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)
d954296py3.8192f5f1chore: Rename fromdeep_geemtodeepgemm📊 Changes
2 files changed (+2 additions, -2 deletions)
View changed files
📝
.github/workflows/publish.yml(+1 -1)📝
setup.py(+1 -1)📄 Description
Since
deep_gemmis already taken on PyPI, we need to change our project name todeepgemm.Background: By default, project name == package name. I.e.
pip install numpy; import numpy.However, some projects diverge:
pip install pillow; import PILSInce deep-gemm is taken, we will now change our strategy from
pip install deep-gemm; import deep_gemmtopip install deepgemm; import deep_demmThe only caveat is that if users believe they need to do
pip install deep-gemmthey 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.