numpy constraint - can it be lifted?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/LAION-AI/CLAP/blame/8e558817d853808486768004fa1b61ac9d69f2a2/pyproject.toml#L24
Most of the TTS/Audio projects I have use numpy >= constraints, except CLAP with ==, which is a requirement of Stable Audio Tools.
How can I test if it's still relevant, and perhaps lift this constraint?
Contributor guide
No contributing guide indexed for this repository
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 by inspecting pyproject.toml at line 24 and identifying what depends on the exact NumPy version. Test CLAP with the constraint relaxed across relevant NumPy versions, and consider the work done when the project installs and operates without regressions under a non-exact constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100