microsoft / microsoft/MInference

[Bug]: minference package is not installable from sdist

Open
#118 0 comments 0 reactions 1 assignee View on GitHub

@iofu728 is already working on this.

Since Feb 12, 2025.

bug
Dominant language
Python
Stars
1.2k
Forks
82
Avg merge
1d 18h
Merged PRs (30d)
1

Description

Describe the bug

I wanted to bring to your attention that the minference package is not installable from sdist. This can be reproduced on any clean system (without pre-installed torch) that has Python, pip, and internet access by running:

pip install minference==0.1.5.post1

A recommended solution would be to migrate from setup.py to pyproject.toml and explicitly declare torch as a build requirement if it is indeed necessary for the build process.

This project has no wheels published on pypi.org. We found wheels on github and tried them out. However the wheels are also broken:

Processing ./cache/minference-0.1.5.post1+cu122torch2.1-cp310-cp310-linux_x86_64.whl
Discarding file:///home/coder/minference-0.1.5.post1/cache/minference-0.1.5.post1%2Bcu122torch2.1-cp310-cp310-linux_x86_64.whl: Requested minference===0.1.5.post1+cu122torch2.1 from file:///home/coder/minference-0.1.5.post1/cache/minference-0.1.5.post1%2Bcu122torch2.1-cp310-cp310-linux_x86_64.whl has inconsistent version: expected '0.1.5.post1+cu122torch2.1', but metadata has '0.1.5.post1'
ERROR: Could not find a version that satisfies the requirement minference===0.1.5.post1+cu122torch2.1 (from versions: 0.1.4, 0.1.4.post1, 0.1.4.post2, 0.1.4.post3, 0.1.4.post4, 0.1.5, 0.1.5.post1, 0.1.5.post1+cu122torch2.1)

for i in $(ls); do unzip -p $i $(unzip -Z1 $i | grep METADATA) | grep '^Version:'; done
Version: 0.1.5.post1
Version: 0.1.5.post1
Version: 0.1.5.post1
Version: 0.1.5.post1

wheel unpack minference-0.1.5.post1+cu122torch2.1-cp38-cp38-linux_x86_64.whl
Missing minference-0.1.5.post1+cu122torch2.1.dist-info/RECORD file

Let me know if you need any additional details. Thanks for your time!

Steps to reproduce

No response

Expected Behavior

No response

Logs

No response

Additional Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.