8000 [3.6] bpo-31592: Fix an assertion failure in Python parser in case of a bad unicodedata.normalize(). (GH-3767) by miss-islington · Pull Request #3836 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

[3.6] bpo-31592: Fix an assertion failure in Python parser in case of a bad unicodedata.normalize(). (GH-3767) #3836

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
Sep 30, 2017
Merged

[3.6] bpo-31592: Fix an assertion failure in Python parser in case of a bad unicodedata.normalize(). (GH-3767) #3836

merged 1 commit into from
Sep 30, 2017

Conversation

miss-islington
Copy link
Contributor
@miss-islington miss-islington commented Sep 30, 2017 •
edited by bedevere-bot
Loading

(cherry picked from commit 7dc46d8)

https://bugs.python.org/issue31592

@orenmn @miss-islington
[3.6] bpo-31592: Fix an assertion failure in Python parser in case of…
c97811b 
… a bad unicodedata.normalize(). (pythonGH-3767)

(cherry picked from commit 7dc46d8)
@bedevere-bot bedevere-bot mentioned this pull request Sep 30, 2017
Merged
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

Thanks again to your contribution and we look forward to looking at it!

@miss-islington
Copy link
Contributor Author

@orenmn and @serhiy-storchaka: Backport status check is done, and it's a success ✅ .

@serhiy-storchaka serhiy-storchaka merged commit a4dfe1c into python:3.6 Sep 30, 2017
@miss-islington
Copy link
Contributor Author
miss-islington 8A47 commented Sep 30, 2017

Thanks, @serhiy-storchaka!

@miss-islington miss-islington deleted the backport-7dc46d8-3.6 branch September 30, 2017 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@miss-islington @the-knights-who-say-ni @serhiy-storchaka @Mariatta @bedevere-bot @orenmn
0