Skip to content

[3.13] gh-120526: Correct signature of map() builtin (GH-120528) #120539

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 1 commit into from
Jun 15, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jun 15, 2024

map() requires at least one iterable arg.

(cherry picked from commit d4039d3)

Co-authored-by: Adam Williamson adam@blueradius.ca
Signed-off-by: Adam Williamson awilliam@redhat.com

map() requires at least one iterable arg.

(cherry picked from commit d4039d3)

Co-authored-by: Adam Williamson <adam@blueradius.ca>
Signed-off-by: Adam Williamson <awilliam@redhat.com>
@ghost
Copy link

ghost commented Jun 15, 2024

All commit authors signed the Contributor License Agreement.
CLA signed

@JelleZijlstra
Copy link
Member

@AdamWill looks like the commit is getting attributed to a different email address; could you sign the CLA with this email address too?

@AdamWill
Copy link
Contributor

Huh, that's weird. Only reason I can think it'd get that email is that it's the primary on my github account, it's not on the original commit at all. I don't mind signing with that address too, but seems like maybe a bug in whatever came with this "co-authored by" attribution?

@serhiy-storchaka serhiy-storchaka merged commit 9f0269d into python:3.13 Jun 15, 2024
34 checks passed
@serhiy-storchaka
Copy link
Member

This is the first time I see this. The original PR was merged, a complain was raised about the backport (which refers to the same email address), but it did not prevent automerging. Did you just sign the CLA for your second address, @AdamWill?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants