Skip to content

Cherry-pick fix for compatibility with Python 3.7#5423

Merged
acozzette merged 1 commit intoprotocolbuffers:3.6.xfrom
acozzette:python-3.7-cherry-pick
Dec 4, 2018
Merged

Cherry-pick fix for compatibility with Python 3.7#5423
acozzette merged 1 commit intoprotocolbuffers:3.6.xfrom
acozzette:python-3.7-cherry-pick

Conversation

@acozzette
Copy link

This cherry-picks the fix from PR #4862 so that we can include it in a 3.6.1.2 patch release.

Compilation of Python wrappers fails with Python 3.7 because
the Python folks changed their C API such that
PyUnicode_AsUTF8AndSize() now returns a const char* rather
than a char*. Add a patch to work around. Relates protocolbuffers#4086.
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

@googlebot googlebot removed the cla: no label Dec 4, 2018
@acozzette
Copy link
Author

The CLA is OK because it was already verified when this fix was merged as part of PR #4862.

@TeBoring
Copy link
Contributor

TeBoring commented Dec 4, 2018

Why #4940 still fail?

@acozzette
Copy link
Author

I'm not sure about #4940 but it looks like those tests are probably failing because of some kind of issue with the test setup and not necessarily a real problem with Python 3.7. The TensorFlow team requested this cherry-pick because they have users who want to upgrade to Python 3.7.

@TeBoring
Copy link
Contributor

TeBoring commented Dec 4, 2018

To build python 3.7, you probably also needs #5406. Otherwise, the built wheel cannot be run on latest mac (usually python 3.7 is on the newest mac)

@acozzette acozzette merged commit d0d9455 into protocolbuffers:3.6.x Dec 4, 2018
@acozzette acozzette deleted the python-3.7-cherry-pick branch December 4, 2018 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants