-
-
Notifications
You must be signed in to change notification settings - Fork 135
Update plugin to support mypy 1.16.0 #2149
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
base: master
Are you sure you want to change the base?
Conversation
This is strange. I haven't seen these issues on my side. 🤔 |
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.
You updated
name = "wemake-python-styleguide"
version = "1.1.0"
Let's pin it to 1.0
for now :)
Oh? I didn't notice. I think I might have just ran |
yes, please :) |
Rebased against master and pinned version |
@sobolevn @Jazzinghen are there any plans to continue work on this PR? |
@svorcan-rho today [email protected] was released :) |
I was waiting for approval after my last commit. Was there something missing? |
the CI is still red, I would be happy to approve it after it is green :) |
I have made things!
Checklist
CHANGELOG.md
Related issues
Closes #2148
I have not updated the readme as there is no strict reference to the supported mypy version, and it looks like the changelog contains release info, so I didn't touch that one either.
All the checks passed, even though I had to add an ignore flag in a function that was using some strange trait-based property access.
I used a solution very similar to the one used in typeddjango/django-stubs#2670 but I get the version info using
importlib
instead of the string in the module.