-
Notifications
You must be signed in to change notification settings - Fork 27
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
Migrate CI to GitHub Actions (v2) #222
base: master
Are you sure you want to change the base?
Conversation
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
mir_eval 0.8.1 is on pypi now; should hit conda-forge by this afternoon. |
add support for python 3.9
i ran the sonify tests and some are failing but for a different reason now. i'll mark those as xfail again and i can investigate and provide more details afterward in the
other than this, i added back the support to python 3.9 by using |
for ns in chain(*map(lambda p: p.rglob('*.json'), resources.files('jams.schemata.namespaces').iterdir())): | ||
schema.add_namespace(ns) | ||
if sys.version_info < (3, 10): | ||
from pkg_resources import resource_filename |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thought that leaving the import statement here might be better than at the beginning of the code to avoid deprecation warning for newer python versions?
based on #217 (unfortunately, i can't add commits to his branch)
changelog
sonify
module. as far i understand, the fix for the errors we were seeing is in the next release (0.8.1)