You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes #1342: numpy / scipy / chonkie version conflict.
Root cause.pyproject.toml [tool.poetry.group.eval] declared scipy = "^1.10.1". scipy 1.10.x pins numpy<1.27.0 (verified via the PyPI JSON metadata), while chonkie>=1.6.0 requires numpy>=2.0.0. The two constraints are jointly unsatisfiable, so any environment that ends up with both packages (the user's reproduction installs chonkie on top of an apt-installed scipy 1.10.x) raises ImportError: numpy.core.multiarray failed to import.
Fix. Bumped the eval-group scipy floor from ^1.10.1 to ^1.13.0 (scipy 1.13 is the first release supporting numpy 2.x) and added two explanatory comments — one near the bumped floor and one above the chonkie entry in the mem-reader extras — so future readers see the numpy 2.x implication.
Scope.scipy is only imported by evaluation/scripts/longmemeval/lme_eval.py and evaluation/scripts/locomo/locomo_eval.py; nothing under src/memos/ references it (grep clean). The change is therefore constraint-only, no source code path is affected.
Verification.ruff check pyproject.toml → "All checks passed!"; ruff format --check pyproject.toml → no diff; pytest tests/chunkers/ → 3 passed in 4.26s; TOML reparsed via tomli.load reports eval scipy= ^1.13.0. The committed poetry.lock already resolves scipy to 1.15.3 / 1.16.0 and numpy to 2.2.6 / 2.3.1, all of which satisfy the new ^1.13.0 floor, so a re-lock would be a no-op and is deferred to the pre-commit poetry-lock hook on the maintainer's machine.
Activity
github-actions commentedon Apr 24, 2026
This issue has been automatically marked as stale due to inactivity.
Memtensor-AI commentedon Jun 29, 2026
🤖 AutoDev has picked up this issue and started working on it.
Task ID:
c114e999523e242aWorking branch:
bugfix/autodev-1342Target branch:
latest dev* branchWorkflow: opsp (analysis → coding → testing → PR)
I will post the PR link here once done. If I need more information, I will ask in the comments.
fix: raise scipy floor to ^1.13.0 for numpy 2.x / chonkie 1.6 compati…
Memtensor-AI commentedon Jun 29, 2026
✅ AutoDev task
c114e999523e242acompleted.Summary: ## Summary
Fixes #1342: numpy / scipy / chonkie version conflict.
Root cause.
pyproject.toml [tool.poetry.group.eval]declaredscipy = "^1.10.1". scipy 1.10.x pinsnumpy<1.27.0(verified via the PyPI JSON metadata), whilechonkie>=1.6.0requiresnumpy>=2.0.0. The two constraints are jointly unsatisfiable, so any environment that ends up with both packages (the user's reproduction installs chonkie on top of an apt-installed scipy 1.10.x) raisesImportError: numpy.core.multiarray failed to import.Fix. Bumped the eval-group scipy floor from
^1.10.1to^1.13.0(scipy 1.13 is the first release supporting numpy 2.x) and added two explanatory comments — one near the bumped floor and one above thechonkieentry in themem-readerextras — so future readers see the numpy 2.x implication.Scope.
scipyis only imported byevaluation/scripts/longmemeval/lme_eval.pyandevaluation/scripts/locomo/locomo_eval.py; nothing undersrc/memos/references it (grep clean). The change is therefore constraint-only, no source code path is affected.Verification.
ruff check pyproject.toml→ "All checks passed!";ruff format --check pyproject.toml→ no diff;pytest tests/chunkers/→ 3 passed in 4.26s; TOML reparsed viatomli.loadreportseval scipy= ^1.13.0. The committedpoetry.lockalready resolves scipy to 1.15.3 / 1.16.0 and numpy to 2.2.6 / 2.3.1, all of which satisfy the new^1.13.0floor, so a re-lock would be a no-op and is deferred to the pre-commitpoetry-lockhook on the maintainer's machine.Base branch:
mainBranch:
bugfix/autodev-1342Commit:
36c24bePR: #1971
Assigned to: @MatthewZhuang, @CarltonXiang, @syzsunshine219, @World-controller
Reviewers: @MatthewZhuang, @CarltonXiang, @syzsunshine219, @World-controller
Fix #1342: [Bug] v2.0.10 依赖冲突: numpy/scipy/chonkie 版本不兼容 (#1971)