Skip to content
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

Use python-typing-update on pylint/pyreverse directory #6309

Merged
merged 1 commit into from
Apr 14, 2022

Conversation

DanielNoord
Copy link
Collaborator

  • Add yourself to CONTRIBUTORS if you are a new contributor.
  • Write a good description on what the PR does.

Type of Changes

Type
βœ“ πŸ”¨ Refactoring

Description

Ref #4683.

@Pierre-Sassoulas @cdce8p Perhaps comment if you're going to review as not to duplicate work.

@DanielNoord DanielNoord added typing Maintenance Discussion or action around maintaining pylint or the dev workflow labels Apr 14, 2022
@DanielNoord DanielNoord added this to the 2.14.0 milestone Apr 14, 2022
@DanielNoord DanielNoord requested a review from cdce8p April 14, 2022 09:08
Tuple[str, str, str, str, int, int],
MessageLocationTuple,
],
location: (tuple[str, str, str, str, int, int] | MessageLocationTuple),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
location: (tuple[str, str, str, str, int, int] | MessageLocationTuple),
location: MessageLocationTuple,

Could we do this ? It seems those should be the same thing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, see the deprecation warning a couple of lines below. location needs to be initialised as MessageLocationTuple and not be a regular tuple.

...

@overload
def __new__(
cls,
msg_id: str,
symbol: str,
location: Tuple[str, str, str, str, int, int],
location: tuple[str, str, str, str, int, int],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
location: tuple[str, str, str, str, int, int],
location: MessageLocationTuple,

(🀞 ?)

@coveralls
Copy link

Pull Request Test Coverage Report for Build 2166275252

  • 38 of 38 (100.0%) changed or added relevant lines in 9 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.002%) to 93.278%

Totals Coverage Status
Change from base Build 2166268905: 0.002%
Covered Lines: 15945
Relevant Lines: 17094

πŸ’› - Coveralls

@DanielNoord DanielNoord merged commit 5bff0d8 into pylint-dev:main Apr 14, 2022
@DanielNoord DanielNoord deleted the 3.7 branch April 14, 2022 09:22
Tuple[str, str, str, str, int, int],
MessageLocationTuple,
],
location: (tuple[str, str, str, str, int, int] | MessageLocationTuple),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The brackets could have been removed here though.

-    location: (tuple[str, str, str, str, int, int] | MessageLocationTuple),
+    location: tuple[str, str, str, str, int, int] | MessageLocationTuple,

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added in follow-up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow typing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants