-
Notifications
You must be signed in to change notification settings - Fork 23
Y068: Don't use @override #528
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
611cdbe
Y068: Don't use @override
srittau d634223
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 2fd34f0
Remove nonsense
srittau 8ad7519
Use _is_object
srittau 1e68e2e
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 89c0287
Improve error code description
srittau cec1170
Fix ERRORCODES.md
srittau 1e0c7d1
Fix ERRORCODES.md
srittau File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,8 @@ | ||
| # Change Log | ||
|
|
||
| New error codes: | ||
| * Introduce Y068: Don't use `@override` in stub files. | ||
|
|
||
| ## 5.5.0 | ||
|
|
||
| New error codes: | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| import typing | ||
| import typing as t | ||
| from typing import override, override as over | ||
|
|
||
| import typing_extensions | ||
|
|
||
| class Foo: | ||
| def f(self) -> None: ... | ||
| def g(self) -> None: ... | ||
| def h(self) -> None: ... | ||
| def j(self) -> None: ... | ||
| def k(self) -> None: ... | ||
|
|
||
| class Bar(Foo): | ||
| @override # Y068 Do not use "@override" in stub files. | ||
| def f(self) -> None: ... | ||
| @typing.override # Y068 Do not use "@override" in stub files. | ||
| def g(self) -> None: ... | ||
| @t.override # Ideally we'd catch this too, but the infrastructure is not in place. | ||
| def h(self) -> None: ... | ||
| @over # Ideally we'd catch this too, but the infrastructure is not in place. | ||
| def j(self) -> None: ... | ||
| @typing_extensions.override # Y068 Do not use "@override" in stub files. | ||
| def k(self) -> None: ... |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
or we could just ban it from being imported by adding a branch to
_check_import_or_attribute, rather than emitting a separate diagnostic on each usage in every stub 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.
I thought about it, but I like this direct approach a bit more: While it may spam a bit in case someone uses it, it's more "direct". "Here's your error", instead of "You're importing something here that's going to be a problem later." It still allows overriding the warning on a case-by-cases basis (although I'm not sure why you would need that). No strong opinion, though.
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 feel like emitting the diagnostic at the location of the import (or attribute access) is more in keeping with our other rules such as Y024 and Y057... but I also don't have a strong opinion :-)
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.
Ok, then let's laziness win and not change it?