Skip to content

fix: widen dependency version ranges to resolve install failures#78

Open
SuperMarioYL wants to merge 1 commit intoNVIDIA:mainfrom
SuperMarioYL:fix/widen-dependency-version-ranges
Open

fix: widen dependency version ranges to resolve install failures#78
SuperMarioYL wants to merge 1 commit intoNVIDIA:mainfrom
SuperMarioYL:fix/widen-dependency-version-ranges

Conversation

@SuperMarioYL
Copy link
Copy Markdown

Motivation

Multiple users report installation failures because dependency upper bounds are too restrictive. For example:

  • huggingface-hub >= 0.24, < 0.25 — latest is 0.30+, any modern environment fails
  • safetensors >= 0.4.0, < 0.5 — latest is 0.5+
  • einops == 0.7 — latest is 0.8+
  • aiohttp >= 3.10.5, < 3.11 — latest is 3.11+

This blocks pip installs unless users manually downgrade everything, which often conflicts with other packages (especially torch ecosystem).

Related: #22, #55, #29, #10, #11

Fix

Remove all restrictive upper bounds, keeping only minimum version floors. The codebase uses only stable, well-established APIs:

Package API Used Stable Since
huggingface-hub hf_hub_download() 0.10+
safetensors load_model(), load_file(), save_file() 0.3+
einops rearrange() 0.1+
numpy Standard array ops 1.x+
sentencepiece SentencePieceProcessor() 0.1+
aiohttp Basic web server 3.x+

None of these APIs have breaking changes in their newer versions.

Scope

Note: PR #63 addresses the torch upper bound separately; PR #76 addresses torch and aiohttp. This PR covers the remaining dependencies not addressed by those PRs.

Changes

File Change
moshi/pyproject.toml Remove upper bounds from all 9 dependencies

Remove restrictive upper bounds from all dependencies in pyproject.toml.
The current pins (e.g., huggingface-hub < 0.25, safetensors < 0.5,
einops == 0.7) prevent installation with modern Python environments
where newer versions of these packages are already installed.

The codebase uses only stable, well-established APIs from each library
(hf_hub_download, safetensors.torch.load_model, einops.rearrange,
numpy array ops, sentencepiece.SentencePieceProcessor) that have
remained backward-compatible across major versions.

Signed-off-by: supermario_leo <[email protected]>
@SuperMarioYL
Copy link
Copy Markdown
Author

Gentle ping on this — happy to rebase onto the latest main or address any feedback. Let me know if there's anything I can adjust to help this move forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant