-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why mediapipe v0.10.15 depends on numpy (<2) and v0.10.14 doesn't? #5612
Comments
Hello @alanwilter |
Many thanks for that. Do you have an idea when |
@alanwilter This will depend on factors like the dependent packages used in MediaPipe(similar to numba package in your project), the stability(as we have already encountered), the performance and acceptable accuracy for each of the supported tasks. Hence, we cannot comment on the timeline for the time being. |
This issue has been marked stale because it has no recent activity since 7 days. It will be closed if no further activity occurs. Thank you. |
How can we prevent this ticket to be automatically closed by the the GitHub Bot? |
Hi @alanwilter, This can be marked as a feature request for supporting NumPy versions>2. We will share it with the team, and based on future demand and discussions, we may proceed with implementation if everything aligns on our end. Thank you!! |
My code is working fine with MP v0.10.14 and numpy v2.0.2.
I can't update to numpy v2.1.1 yet because I use numba, whose v0.60.0, is not yet updated for latest numpy.
Anyway, when I was trying to update to latest MP, I got this warning.
Was this pinning introduced on purpose to address some particular issue?
The text was updated successfully, but these errors were encountered: