-
Notifications
You must be signed in to change notification settings - Fork 193
Conversation
- Using ruff and stricter pyright settings. Will have to remove later.
- Leave two extra pyright settings on — they can't hurt, right?
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.
I know this is still in draft but some things to note so far.
- Not as sure on the relative import change. In my opinion, this is a clearer indicator of where the imports are coming from, is more consistent with similar imports in other files, and doesn't run the risk of messing with an import of builtin types module, unlikely as that is to happen. Might be a matter of style though.
Maybe more could be done, but this feels like it could be enough for a PR that doesn't add functionality. |
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.
Looks good to me, waiting for @EvieePy for final review.
Has this been tested in terms of actually being able to be ran? With like simple.py or something? |
Yep. It works fine with simple.py on my machine, though I didn't run it exhaustively — I loaded up "Ocean Drive" and a "Rock Classics" Spotify playlist (courtesy of the examples in the migrating docs) and just let it go for a while. |
Ideally, this doesn't result in any change to the functionality; it's more about making the typing syntax consistent with python 3.10+ and ensuring pyright flags it accordingly if it isn't.