microsoft / microsoft/microxcaling
Consider a PyPI package?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 364
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Our package https://github.com/graphcore-research/gfloat would like to depend on mx, but currently has to include it in requirements.txt as a direct dependency:
# Requirements for tests
pytest
ml_dtypes
mx @ git+https://github.com/microsoft/microxcaling
Normally, I think this is a good idea - one knows exactly what code one is depending on, etc.
However, pypi says
Can't have direct dependency: mx@ git+https://github.com/microsoft/microxcaling ;
extra == "dev". See https://packaging.python.org/specifications/core-metadata for
more information.
And this seems hard to fix (see the "amusing side effect" at https://stackoverflow.com/a/54894359)
If microxscaling could be a PyPI package we would not need the direct dependency.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the requirements.txt entry shown in the issue and review PyPI's direct-URL dependency restrictions. Done would mean microxcaling is available as a PyPI package so graphcore-research/gfloat can depend on it without the direct Git URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100