-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-43918: document signature and default argument of anext
builtin
#25551
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
Conversation
Co-authored-by: Dennis Sweeney <36520290+sweeneyde@users.noreply.github.com>
This PR is stale because it has been open for 30 days with no activity. |
The test failure seemed intermittent and unrelated. How do we rerun the tests? Other than the failed checks, this should be ready to merge, right? |
Close and reopen the PR. |
👍 Restarted and tests now pass. There are two workflows awaiting approval before they can run. |
Sorry for the slow response! I will land once tests fail. |
s/fail/pass/ :-) |
How long has that address sanitizer CI run been hanging? Is it perhaps time to restart the tests again (via close + reopen PR)? |
@gvanrossum: Please replace |
As described at https://bugs.python.org/issue43918, the new
anext
builtin doesn't include any signature information.help(anext)
should show something likeanext(aiterator[, default])
, which is added in this PR.I also added text describing the
default
argument as I understand it. This text was adapted fromnext
. See the description in the documentation here: https://github.com/python/cpython/pull/23847/files#diff-6a7a07ac473fdd76734669b1b70626ad2176011129902f6add017810f54d0439R87I ran the clinic on " Python/bltinmodule.c".
Alright, now I need to figure out how to add a blurb...
https://bugs.python.org/issue43918