We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now this code is not an error:
class A: def some(self) -> int: ... class B(A): def some(self) -> int: ...
But, it is not a good style. I propose to add a check for this. Related python/typeshed#7073
The text was updated successfully, but these errors were encountered:
I agree that this would be great. It might be tricky to implement (but my mind is already racing with ideas about how to do it 😀).
We would also have to exclude dunder methods, because we would get a lot of false positives (see discussion in python/typeshed#6877).
Sorry, something went wrong.
Offtopic, @AlexWaygood if you are intersted in flake8 plugins, I welcome you giving https://github.com/wemake-services/wemake-python-styleguide a try. It has lots of open feature requests (all are pretty non-trivial).
flake8
I'll add it to my to-do list 😄
As discussed in python/mypy#13321, this check would be a better fit for a linter that can harness the power of a type checker; let's do that instead.
No branches or pull requests
Right now this code is not an error:
But, it is not a good style. I propose to add a check for this.
Related python/typeshed#7073
The text was updated successfully, but these errors were encountered: