-
Notifications
You must be signed in to change notification settings - Fork 3
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
Drop support for Python 3.9 #130
Conversation
I see no changes in the file |
Well spotted! :D I was thinking about changing that too, but I don't think it's really worth changing. For one thing, just partially matching the error message is sufficient I think, and also it's a test for a deprecated function that will be removed soon, anyway. (Actually, I think it's probably a good time to remove it in the upcoming release, it's been deprecated for a while and I don't think it's still used anywhere in our projects... But that's for another PR ^^) |
This PR removes support for Python 3.9, raising the minimum Python version to 3.10, in order to allow for more modern typing (union types with
X | Y
), and modernizes the code base.Additionally, this allowed us to remove a rather hacky workaround that was needed for Python < 3.10, where dataclasses did not support
kw_only
yet. This also removes the need forcoverage-conditional-plugin
.I also updated the testing dependencies.
This qualifies as a breaking change in terms of Python version compatibility. There are no breaking API changes, however.