bpo-31393: Fix the use of PyUnicode_READY().#3451
Merged
serhiy-storchaka merged 1 commit intoSep 8, 2017
Merged
Conversation
serhiy-storchaka
added
needs backport to 3.6
type-bug
benjaminp
approved these changes
Sep 8, 2017
Contributor
|
🐍🍒⛏🤖 Thanks @serhiy-storchaka for the PR, and @serhiy-storchaka for merging it 🌮🎉.I'm working now to backport this PR to: 3.6. |
Contributor
|
Sorry, @serhiy-storchaka and @serhiy-storchaka, I could not cleanly backport this to |
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this pull request
Sep 8, 2017
(cherry picked from commit e3b2b4b)
|
GH-3453 is a backport of this pull request to the 3.6 branch. |
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
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://bugs.python.org/issue31393