8000 bpo-41215: Don't use NULL by default in the PEG parser keyword list by pablogsal · Pull Request #21355 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

bpo-41215: Don't use NULL by default in the PEG parser keyword list #21355

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 2 commits into from
Jul 6, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
< 8000 /form>
Diff view
Prev Previous commit
Update Misc/NEWS.d/next/Core and Builtins/2020-07-06-18-36-33.bpo-41215
….vFGFIz.rst

Co-authored-by: Lysandros Nikolaou <lisandrosnik@gmail.com>
  • Loading branch information
pablogsal and lysnikolaou authored Jul 6, 2020
commit 668965433fa3b4ce5ac7ba7fb72b094b30621d0a
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
Use non-NULL default values in the PEG parser keyword list to overcome a bug that was preventing
Python to be properly compiled when using the XLC compiler. Patch by Pablo Galindo.
Python from being properly compiled when using the XLC compiler. Patch by Pablo Galindo.
0