-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-41215: Don't use NULL by default in the PEG parser keyword list #21355
Conversation
Misc/NEWS.d/next/Core and Builtins/2020-07-06-18-36-33.bpo-41215.vFGFIz.rst
Outdated
Show resolved
Hide resolved
…15.vFGFIz.rst Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
@lysnikolaou Wanna land this one and the other yourself 😉 ? |
I was kinda hoping you'd say that! Let me try the |
We should remove the |
GH-21356 is a backport of this pull request to the 3.9 branch. |
…list (GH-21355) (GH-21356) (cherry picked from commit 39e76c0) Co-authored-by: Pablo Galindo <pablogsal@gmail.com> Automerge-Triggered-By: @lysnikolaou
@pablogsal: Status check is done, and it's a success ✅ . |
Worked like a charm. |
Awesome 🎉 |
…ythonGH-21355) Automerge-Triggered-By: @lysnikolaou
https://bugs.python.org/issue41215
Automerge-Triggered-By: @lysnikolaou