Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add hint for AsyncIterator incompatible return type#15883

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
hauntsaninja merged 2 commits intopython:masterfromikonst:async-iterator-hint
Aug 30, 2023

Conversation

@ikonst
Copy link
Contributor

For issue described in#5070 and documented in#14973, add a contextual link to the docs.

@github-actions
Copy link
Contributor

According tomypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅

@ikonst
Copy link
ContributorAuthor

@hauntsaninja OK on the approach? If so, I'll also add the same treatment tosignature_incompatible_with_supertype


class Launcher(P):
def launch(self) -> AsyncIterator[int]: # E: Return type "AsyncIterator[int]" of "launch" incompatible with return type "Coroutine[Any, Any, AsyncIterator[int]]" in supertype "P" \
# N: Consider declaring "launch" in supertype "P" without "async" \
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't it instead say: "consider addingasync todef lauch()"?

Because in my experience, AsyncIterators are way more common withasync def rather than regulardef

Copy link
ContributorAuthor

@ikonstikonstAug 29, 2023
edited
Loading

Choose a reason for hiding this comment

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

Ehh, this is confusing :|

The 'problem' here should really be reported on this line:

  class P(Protocol):!>    async def launch(self) -> AsyncIterator[int]:         raise BaseException

but we don't put notices proactively on declarations that smell funny, or do we?

The error on the derivedLauncher.launch gives us the excuse to make a notice. What we want to say is "listen, we must error onLauncher.launch, butLauncher.launch is probably fine, consider changing the base declaration instead".

Copy link
Collaborator

@hauntsaninjahauntsaninja left a comment

Choose a reason for hiding this comment

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

Thanks! I think test case might be little less confusing if it used yield to showcase the common issue, but should all work the same

@hauntsaninjahauntsaninja merged commita7e0f6f intopython:masterAug 30, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@sobolevnsobolevnsobolevn left review comments

@hauntsaninjahauntsaninjahauntsaninja approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ikonst@sobolevn@hauntsaninja

[8]ページ先頭

©2009-2025 Movatter.jp