ByteDance-Seed / ByteDance-Seed/Depth-Anything-3
Is there a reason to use numpy <2?
- Dominant language
- Python
- Stars
- 6.3k
- Forks
- 702
- PR merge metrics
- No merged PRs in 30d
Description
Hey, team, currently Depth Anything v3 requires numpy library to be <2 which causes dependency conflict with other packages (such as python-opencv which requires numpy>=2). Is there a particular reason that numpy>=2.0 cannot be used? Note that Depth Anything v2 supports numpy>=2.0.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the project’s NumPy dependency declaration and compare it with the Depth Anything v2 requirement mentioned in the issue. Check whether the Depth Anything 3 code has any NumPy version constraints, then verify installation alongside python-opencv; the work is done when the compatibility reason is established and the dependency requirements are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, opencv, python
- Domain
- build-system, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100