-
Notifications
You must be signed in to change notification settings - Fork 116
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
update numpy dependency #352
Labels
Milestone
Comments
👍 to this - should be an easy update if anyone wants to prep a PR? |
+1, PRs welcome! |
Think this is resolved now (but might be wrong). |
Related #366 |
Open
I am the maintainer of your package on Debian.
Notice that you made several changes to mir_eval.
Debian robots track your changes here
https://github.com/craffel/mir_eval/releases
However, this url states that the last change was on 02/16/2022.
Would you be able to release a new version with all these changes, so that I can update mir_eval?
Grateful!
Nilson F. Silva
…________________________________
De: Colin Raffel ***@***.***>
Enviado: segunda-feira, 25 de março de 2024 15:54
Para: craffel/mir_eval ***@***.***>
Cc: Nilsonfsilva ***@***.***>; Author ***@***.***>
Assunto: Re: [craffel/mir_eval] update numpy dependency (Issue #352)
Closed #352<#352> as completed via #370<#370>.
—
Reply to this email directly, view it on GitHub<#352 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVZIS74TNUBQYJ5FYIDFWM3Y2BXFRAVCNFSM6AAAAAAT5PICL2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGIZTSMJWGM2TSNY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@Nilsonfsilva There's a milestone set up for the next release, and I'm working on it. |
I'll be waiting!
Nilson F. Silva
…________________________________
De: Brian McFee ***@***.***>
Enviado: segunda-feira, 25 de março de 2024 16:57
Para: craffel/mir_eval ***@***.***>
Cc: Nilsonfsilva ***@***.***>; Mention ***@***.***>
Assunto: Re: [craffel/mir_eval] update numpy dependency (Issue #352)
@Nilsonfsilva<https://github.com/Nilsonfsilva> There's a milestone set up for the next release, and I'm working on it.
—
Reply to this email directly, view it on GitHub<#352 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVZIS74T4VQUQDCH6D56RS3Y2B6RTAVCNFSM6AAAAAAT5PICL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYHAYDCMBWGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
guillaumekh
added a commit
to guillaumekh/jams
that referenced
this issue
Jul 4, 2024
note: - [email protected] dropped support for Python <= 3.8 - [email protected]+ broke mir_eval. A fix was merged in mir_eval@main but has not been released yet - see: mir-evaluation/mir_eval#352 - [email protected] brakes mir_eval - see: mir-evaluation/mir_eval#383 - i updated pytest hoping it would help solve failing tests but that's a HUGE v3—>v8 jump. I only made the bare minimum of fixes to accomodate this upgrade, and I would expect more work is needed - i wanted to add python 11/12 support but delayed this until we can already get tests runnning properly on 3.9/3.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
As you know, your project is on Debian.
Recently, one of your code's dependencies was updated, in this case "numpy".
As debian is constantly updating its packages, mir-herval also needed to make some changes to some parts of its code in order to keep it building normally.
This issue is described in this article:
https://levelup.gitconnected.com/fix-attributeerror-module-numpy-has-no-attribute-float-d7d68c5a4971
Below is part of the code that needed updates:
The text was updated successfully, but these errors were encountered: