Skip to content

[3.6] bpo-33595: Fix lambda parameters being refered as arguments (GH-7037) #7041

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
May 22, 2018

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented May 22, 2018

(cherry picked from commit 268cc7c)

Co-authored-by: Andrés Delfino adelfino@gmail.com

https://bugs.python.org/issue33595

(cherry picked from commit 268cc7c)

Co-authored-by: Andrés Delfino <adelfino@gmail.com>
@miss-islington
Copy link
Contributor Author

@andresdelfino and @JulienPalard: Backport status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

Thanks!

@miss-islington miss-islington deleted the backport-268cc7c-3.6 branch May 22, 2018 08:07
@terryjreedy terryjreedy changed the title [3.6] Fix lambda parameters being refered as arguments (GH-7037) [3.6] bpo-33595: Fix lambda parameters being refered as arguments (GH-7037) May 25, 2018
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.

5 participants