-
Notifications
You must be signed in to change notification settings - Fork 400
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
match d43, d65, etc. #1363
match d43, d65, etc. #1363
Conversation
We have no-self-use disabled in the music21 pylint configuration. Make sure that pylint is reading the file. |
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.
Great! Some small and fast changes then ready to go. Thanks!
I don't see it in the .pylintrc in the repository root directory. Is there more pylint configuration elsewhere? |
Ah! For various reasons, we have to put the configuration in twice -- once in music21/test/testLint.py and once in the .pylintrc -- they're supposed to be kept perfectly in sync, but obviously they weren't for this point. |
Looking good. Letting tests run (I should've had you do a one-byte PR to get you approved as not "first-time-contributor" long ago), and if all pass will merge. THANKS! |
As you can see the tests are failing with the same error I referenced in #1267; any suggestions for what might be going on with that are welcome. |
It's the 3.10.6 change that was causing the failure. Fix pushed and running tests again. |
Ah -- no-self-use was moved to an optional extension in recent versions of pylint, and is no longer checked. So the solution is to upgrade your pylint. |
Merged. Congrats! |
I went ahead and implemented a regex to make other inversions prefaced by "d" also dominant seventh chords as I suggested in #1358. It was just a couple lines of code and it will allow me to clean up some of the stray chords still not matching with the tsvConverter.
NB pylint objects
music21/roman.py:2378: [R0201(no-self-use), RomanNumeral._findSemitoneSizeForQuality] Method could be a function
but this is not code introduced by me.My remaining question is: perhaps 'd' should indicate dominant seventh quality no matter what digits follow? I.e., if a user indicates something weird like "d479', we should just pass the digits straight through but set impliedQuality to 'dominant-seventh'?