bpo-35973: Fix potential memory leak in parsetok.c by pablogsal · Pull Request #11832 · python/cpython
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 34.4k
Merged
pablogsal merged 1 commit intopython:masterfrom
Feb 13, 2019Merged
bpo-35973: Fix potential memory leak in parsetok.c#11832
pablogsal merged 1 commit intopython:masterfrom
bpo-35973: Fix potential memory leak in parsetok.c#11832
pablogsal merged 1 commit intopython:masterfrom
Conversation
Copy link Copy Markdown
Member
the-knights-who-say-ni
added
the
CLA signed
label
bedevere-bot
added
the
awaiting merge
label
pablogsal
added
the
skip news
label
gvanrossum approved these changes Feb 13, 2019
Copy link Copy Markdown
Member
gvanrossum
left a comment
gvanrossum
left a comment
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup. Thanks!
pablogsal
merged commit
b9d2e97
into
python:master
bedevere-bot
removed
the
awaiting merge
label
pablogsal
deleted the
bpo35973
branch
Copy link Copy Markdown
Member
gvanrossum
commented
Feb 13, 2019
gvanrossum commented
Feb 13, 2019@pablogsal: Somehow the bpo designation dropped off the commit, I closed the issue manually.
This 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