Skip to content
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.

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

[2.7] bpo-31271: Fix an assertion failure in io.TextIOWrapper.write. (GH-3201) #3611

Closed

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Sep 16, 2017

(cherry picked from commit a5b4ea1)

https://bugs.python.org/issue31271

@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!

Copy link
Member

@serhiy-storchaka serhiy-storchaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know whether it is worth to backport this change, but if do this, unicode should be accepted.

@@ -1301,6 +1301,13 @@ textiowrapper_write(textio *self, PyObject *args)
Py_DECREF(text);
if (b == NULL)
return NULL;
if (!PyBytes_Check(b)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unicode should be accepted too. _PyBytes_Join() in 2.7 supports unicode objects.

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I didn't expect the Spanish Inquisition!. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@Mariatta
Copy link
Member

Thanks @serhiy-storchaka.
@miss-islington won't be making the requested change (she is a bot), and I'm not familiar with C at all.
If no one else willing to backport to 2.7, maybe we can close the issue. I'll let you make that call :)

@serhiy-storchaka
Copy link
Member

Ah, I noticed that @miss-islington created a backporting PR, then it was closed and somebody created a new backporting PR. I missed that it was @miss-islington again!

@Mariatta
Copy link
Member

Yes sorry I mistakenly closed the other backport PR so I made miss-islington create another one... :(

@vstinner
Copy link
Member

vstinner commented Oct 2, 2017

@serhiy-storchaka: What should we do with this PR? Close it? The bot is not going to update its PR according to your review :-)

@serhiy-storchaka
Copy link
Member

I think it should be closed after creating a correct backport. Otherwise we risk to lose it. Re-adding the "needs backport to 2.7" label in #3201 will just trigger creating yet one incorrect backport.

@serhiy-storchaka
Copy link
Member

As @orenmn pointed on the tracker, the code is correct. Only the test need to be fixed.

@Mariatta
Copy link
Member

I'm closing this since the proper backport with tests passing has been done in #3951.

@Mariatta Mariatta closed this Oct 22, 2017
@miss-islington miss-islington deleted the backport-a5b4ea1-2.7 branch October 22, 2017 17:28
@serhiy-storchaka
Copy link
Member

Thanks @Mariatta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants