Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[3.8] bpo-36290: Fix keyword collision handling in AST node constructors (GH-12382) #20366

Merged
merged 1 commit into from
May 24, 2020
Merged

[3.8] bpo-36290: Fix keyword collision handling in AST node constructors (GH-12382) #20366

merged 1 commit into from
May 24, 2020

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented May 24, 2020 •
edited by bedevere-bot
Loading

(cherry picked from commit c73914a)

Co-authored-by: Rémi Lapeyre remi.lapeyre@lenstra.fr

https://bugs.python.org/issue36290

@remilapeyre @miss-islington
bpo-36290: Fix keytword collision handling in AST node constructors (p…
14e22e6 
…ythonGH-12382)

(cherry picked from commit c73914a)

Co-authored-by: Rémi Lapeyre <remi.lapeyre@lenstra.fr>
@bedevere-bot bedevere-bot mentioned this pull request May 24, 2020
Merged
@lysnikolaou lysnikolaou mentioned this pull request May 24, 2020
Merged
@miss-islington
Copy link
Contributor Author

@remilapeyre and @pablogsal: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 907ee1f into python:3.8 May 24, 2020
@miss-islington miss-islington deleted the backport-c73914a-3.8 branch May 24, 2020 21:31
@miss-islington
Copy link
Contributor Author

@remilapeyre and @pablogsal: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@remilapeyre and @pablogsal: Status check is done, and it's a success ✅ .

@pablogsal pablogsal changed the title [3.8] bpo-36290: Fix keytword collision handling in AST node constructors (GH-12382) [3.8] bpo-36290: Fix keyword collision handling in AST node constructors (GH-12382) May 24, 2020
@miss-islington
Copy link
Contributor Author

@remilapeyre and @pablogsal: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@remilapeyre and @pablogsal: Status check is done, and it's a success ✅ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pablogsal pablogsal pablogsal 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.
5 participants
@miss-islington @pablogsal @the-knights-who-say-ni @bedevere-bot @remilapeyre