Skip to content

[2.7] bpo-35068: Fix possible crashes in pyexpat.c #10099

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 29, 2018
Merged

[2.7] bpo-35068: Fix possible crashes in pyexpat.c #10099

merged 1 commit into from
Oct 29, 2018

Conversation

ZackerySpytz
Copy link
Contributor

@ZackerySpytz ZackerySpytz commented Oct 25, 2018 •
edited by bedevere-bot
Loading

@ZackerySpytz ZackerySpytz force-pushed the 2.7-pyexpat.c-possible-crashes branch from 13efbce to 0d12dc0 Compare October 25, 2018 17:13
@serhiy-storchaka serhiy-storchaka added type-bug An unexpected behavior, bug, or error skip news labels Oct 29, 2018
@serhiy-storchaka serhiy-storchaka merged commit d61f586 into python:2.7 Oct 29, 2018
@ZackerySpytz ZackerySpytz deleted the 2.7-pyexpat.c-possible-crashes branch October 29, 2018 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@serhiy-storchaka serhiy-storchaka serhiy-storchaka approved these changes

Assignees
No one assigned
Labels
skip news type-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ZackerySpytz @serhiy-storchaka @the-knights-who-say-ni @bedevere-bot