bpo-36030: Fix a possible segfault in PyTuple_New() by ZackerySpytz · Pull Request #15670 · python/cpython
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 34.4k
Merged
vstinner merged 1 commit intopython:masterfrom
Sep 4, 2019Merged
bpo-36030: Fix a possible segfault in PyTuple_New()#15670
vstinner merged 1 commit intopython:masterfrom
bpo-36030: Fix a possible segfault in PyTuple_New()#15670
vstinner merged 1 commit intopython:masterfrom
Conversation
Copy link Copy Markdown
Contributor
the-knights-who-say-ni
added
the
CLA signed
label
bedevere-bot
added
the
awaiting review
label
sir-sigurd approved these changes Sep 4, 2019
bedevere-bot
added
awaiting core review
and removed
awaiting review
labels
vstinner
added
the
skip news
label
vstinner
merged commit
60bd1f8
into
python:master
bedevere-bot
removed
the
awaiting core review
label
lisroach pushed a commit to lisroach/cpython that referenced this pull request
Sep 10, 2019DinoV pushed a commit to DinoV/cpython that referenced this pull request
Jan 14, 2020websurfer5 pushed a commit to websurfer5/cpython that referenced this pull request
Jul 20, 2020This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment