bpo-43751: Fix anext() bug where it erroneously returned None#25238
Conversation
|
There are a bunch of problems in the CI. The main one is: and there is also some trailing whitespace. Could you check these? |
Sorry, something went wrong.
|
This should probably have been a draft PR. I wrote a test for the erroneous None returns, then fixed it. And then I applied the same test to async iterables that are not generators, and that is still failing. |
Sorry, something went wrong.
|
This should be ready for review now. |
Sorry, something went wrong.
jab
left a comment
There was a problem hiding this comment.
Thanks for catching this!
Sorry, something went wrong.
|
Side comment on the PR title: please don't use "should no longer". Say something like "Fix anext() bug where it erroneously returned None". |
Sorry, something went wrong.
Fix inconsistent variable names in comment Co-authored-by: Joshua Bronson <jabronson@gmail.com>
|
I'm requesting that someone else reviews this instead of me. @pablogsal? @1st1? |
Sorry, something went wrong.
…use awaitable is always a coroutine in that case.
|
|
Sorry, something went wrong.
https://bugs.python.org/issue43751