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.

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

[3.9] bpo-41215: Don't use NULL by default in the PEG parser keyword list (GH-21355) #21356

Merged
merged 2 commits into from
Jul 6, 2020

Conversation

pablogsal
Copy link
Member

@pablogsal pablogsal commented Jul 6, 2020

(cherry picked from commit 39e76c0)

Co-authored-by: Pablo Galindo pablogsal@gmail.com

https://bugs.python.org/issue41215

Automerge-Triggered-By: @lysnikolaou

…list.

(cherry picked from commit 39e76c0)

Co-authored-by: Pablo Galindo <pablogsal@gmail.com>
…15.vFGFIz.rst

Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
@lysnikolaou lysnikolaou changed the title [3.9] bpo-41215: Don't use NULL by default in the PEG parser keyword … [3.9] bpo-41215: Don't use NULL by default in the PEG parser keyword list (GH-21355) Jul 6, 2020
@miss-islington
Copy link
Contributor

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

@miss-islington miss-islington merged commit 54f115d into python:3.9 Jul 6, 2020
@pablogsal pablogsal deleted the backport-39e76c0-3.9 branch May 19, 2021 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants