deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[GH-ISSUE #219] Package name change #125

New issue
Closed
opened 2026-10-26 21:13:12 +00:00 by bsakaguchi · 6 comments
bsakaguchi commented 2026-10-26 21:13:12 +00:00
Owner
Copy link

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

Hi! In 9528451969 (which was included in v2.1.1.post1), the name of the library was changed from deep-gemm to deepgemm. This causes a lot of issues for downstream users of this library that specify it as a dependency (or import it) using the old name, resulting in broken builds and invalid import statements, necessitating expensive workarounds or migrations.

In https://github.com/deepseek-ai/DeepGEMM/pull/217, it was noted that this name change is necessary since the name is already taken on PyPI, but instead of changing the name it might be better to try to reclaim that name in PyPI. You could consider asking the PyPI package owner if they can transfer the package to you, or file a PEP541 support request in https://github.com/pypi/support to use the original name since to prevent name confusion attacks.

Let me know if you need assistance with either of these approaches; I think it would benefit the community to keep the package name the same going forward. Thank you!

Originally created by @mprpic on GitHub (Oct 15, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/219 Hi! In 9528451969bba06b67947a31fd9b38126d5e8a73 (which was included in v2.1.1.post1), the name of the library was changed from `deep-gemm` to `deepgemm`. This causes a lot of issues for downstream users of this library that specify it as a dependency (or import it) using the old name, resulting in broken builds and invalid import statements, necessitating expensive workarounds or migrations. In https://github.com/deepseek-ai/DeepGEMM/pull/217, it was noted that this name change is necessary since the name is already taken on PyPI, but instead of changing the name it might be better to try to reclaim that name in PyPI. You could consider asking the PyPI package owner if they can transfer the package to you, or file a PEP541 support request in https://github.com/pypi/support to use the original name since to prevent name confusion attacks. Let me know if you need assistance with either of these approaches; I think it would benefit the community to keep the package name the same going forward. Thank you!
bsakaguchi commented 2026-10-26 21:13:14 +00:00
Author
Owner
Copy link

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

Hey @mprpic, I'm checking.

Could you share an error message? I'm surprised by this, imports (import deep_gemm) shouldb be affected by this. Which scenario are you running into?

<!-- gh-comment-id:3406626282 --> @ko3n1g commented on GitHub (Oct 15, 2025): Hey @mprpic, I'm checking. Could you share an error message? I'm surprised by this, imports (`import deep_gemm`) shouldb be affected by this. Which scenario are you running into?
bsakaguchi commented 2026-10-26 21:13:14 +00:00
Author
Owner
Copy link

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

I.e. the following still works fine:

root@6ca8e17390fb:/# pip install --no-build-isolation  git+https://github.com/deepseek-ai/DeepGEMM.git
Collecting git+https://github.com/deepseek-ai/DeepGEMM.git
  Cloning https://github.com/deepseek-ai/DeepGEMM.git to /tmp/pip-req-build-6ez6eedc
  Running command git clone --filter=blob:none --quiet https://github.com/deepseek-ai/DeepGEMM.git /tmp/pip-req-build-6ez6eedc
  Resolved https://github.com/deepseek-ai/DeepGEMM.git to commit 2b8a8e24f8964fa2f7a74f435bf2975dea56950a
  Running command git submodule update --init --recursive -q
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: deepgemm
  DEPRECATION: Building 'deepgemm' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'deepgemm'. Discussion can be found at https://github.com/pypa/pip/issues/6334
  Building wheel for deepgemm (setup.py) ... done
  Created wheel for deepgemm: filename=deepgemm-2.1.1+2b8a8e2-cp312-cp312-linux_x86_64.whl size=8507544 sha256=7424195ae68bbafbb2e66ea06851ddc2150ad2f84de1182c6e80ad2c409b1e1f
  Stored in directory: /tmp/pip-ephem-wheel-cache-2w0ekps7/wheels/7c/82/61/6ae0658158d61b3f52b97c7fbde3c7be237f97a2601025fe5c
Successfully built deepgemm
Installing collected packages: deepgemm
Successfully installed deepgemm-2.1.1+2b8a8e2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
root@6ca8e17390fb:/# python
Python 3.12.3 (main, Feb  4 2025, 14:48:35) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import deep_gemm
>>>
<!-- gh-comment-id:3406628673 --> @ko3n1g commented on GitHub (Oct 15, 2025): I.e. the following still works fine: ``` root@6ca8e17390fb:/# pip install --no-build-isolation git+https://github.com/deepseek-ai/DeepGEMM.git Collecting git+https://github.com/deepseek-ai/DeepGEMM.git Cloning https://github.com/deepseek-ai/DeepGEMM.git to /tmp/pip-req-build-6ez6eedc Running command git clone --filter=blob:none --quiet https://github.com/deepseek-ai/DeepGEMM.git /tmp/pip-req-build-6ez6eedc Resolved https://github.com/deepseek-ai/DeepGEMM.git to commit 2b8a8e24f8964fa2f7a74f435bf2975dea56950a Running command git submodule update --init --recursive -q Preparing metadata (setup.py) ... done Building wheels for collected packages: deepgemm DEPRECATION: Building 'deepgemm' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'deepgemm'. Discussion can be found at https://github.com/pypa/pip/issues/6334 Building wheel for deepgemm (setup.py) ... done Created wheel for deepgemm: filename=deepgemm-2.1.1+2b8a8e2-cp312-cp312-linux_x86_64.whl size=8507544 sha256=7424195ae68bbafbb2e66ea06851ddc2150ad2f84de1182c6e80ad2c409b1e1f Stored in directory: /tmp/pip-ephem-wheel-cache-2w0ekps7/wheels/7c/82/61/6ae0658158d61b3f52b97c7fbde3c7be237f97a2601025fe5c Successfully built deepgemm Installing collected packages: deepgemm Successfully installed deepgemm-2.1.1+2b8a8e2 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. root@6ca8e17390fb:/# python Python 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import deep_gemm >>> ```
bsakaguchi commented 2026-10-26 21:13:15 +00:00
Author
Owner
Copy link

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

Ah, the import statements work indeed, sorry about that. At Red Hat, we use https://github.com/python-wheel-build/fromager to build wheels of certain AI/ML libraries, and the resulting wheel name is thus different so it breaks our build because it expects the old name for a version-unconstrained inclusion of this library in a requirements file. To be able to support the new name, we'd have to maintain two different versions and two different names for the same code in our build definitions for this specific library.

<!-- gh-comment-id:3406678913 --> @mprpic commented on GitHub (Oct 15, 2025): Ah, the import statements work indeed, sorry about that. At Red Hat, we use https://github.com/python-wheel-build/fromager to build wheels of certain AI/ML libraries, and the resulting wheel name is thus different so it breaks our build because it expects the old name for a version-unconstrained inclusion of this library in a requirements file. To be able to support the new name, we'd have to maintain two different versions and two different names for the same code in our build definitions for this specific library.
bsakaguchi commented 2026-10-26 21:13:15 +00:00
Author
Owner
Copy link

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

Oh that's a fair point, system's depending on the wheel-name will have a bad day. Apologies, I'll open a revert right away. I'm a bit pessimistic on the PyPI transfer but I'll give it a try.

Thanks for the quick issue!

<!-- gh-comment-id:3406735543 --> @ko3n1g commented on GitHub (Oct 15, 2025): Oh that's a fair point, system's depending on the wheel-name will have a bad day. Apologies, I'll open a revert right away. I'm a bit pessimistic on the PyPI transfer but I'll give it a try. Thanks for the quick issue!
bsakaguchi commented 2026-10-26 21:13:15 +00:00
Author
Owner
Copy link

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

This library has almost 6k stars here on GitHub, so it seems fair that you should own the same package name in PyPI to prevent package name confusion. Let me know if you'd like help with filing the requests to PyPI. Thank you for the quick action!

<!-- gh-comment-id:3406755395 --> @mprpic commented on GitHub (Oct 15, 2025): This library has almost 6k stars here on GitHub, so it seems fair that you should own the same package name in PyPI to prevent package name confusion. Let me know if you'd like help with filing the requests to PyPI. Thank you for the quick action!
bsakaguchi commented 2026-10-26 21:13:16 +00:00
Author
Owner
Copy link

@mprpic commented on GitHub (Oct 20, 2025):

Closing this in favor of: https://github.com/pypi/support/issues/7898

<!-- gh-comment-id:3422063399 --> @mprpic commented on GitHub (Oct 20, 2025): Closing this in favor of: https://github.com/pypi/support/issues/7898
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
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#125
No description provided.