Trim heavy dependencies: reconsider hard scikit-learn dependency for KMeans-only usage
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 114
- Avg merge
- 19h 14m
- Merged PRs (30d)
- 1
Description
This appears to be a hard dependency purely for KMeans used in initialization for HMMs. Pulling in sklearn as a top-level dependency brings in a large, non-JAX dependency chain for what's a single clustering call used at init time.
Can an HMM extra be added, and sklearn can be moved over to it?
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
Inspect the package dependency configuration and the HMM initialization path that uses KMeans. Confirm which dependency is needed for a base installation versus the HMM extra, then verify that the extra provides scikit-learn and that HMM initialization still works without it installed by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, scikit-learn
- Domain
- build-system, machine-learning
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100