apache-spark 2.1.0: patch to work with python 3.6 #12059
Closed
Conversation
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
liudangyi
force-pushed
the
spark-python3.6
branch
from
8eee0a5 to
b81e888
Compare
ilovezfs
force-pushed
the
spark-python3.6
branch
from
b81e888 to
9f46eef
Compare
bfontaine
reviewed
Apr 25, 2017
| bottle :unneeded | ||
|
|
||
| patch do | ||
| url "https://github.com/apache/spark/pull/16429.patch" |
There was a problem hiding this comment.
You should be able to use the commit URL instead now that the PR has been merged: https://github.com/apache/spark/commit/20e6280626fe243b170a2e7c5e018c67f3dac1db.patch
|
Could you rebase this, and make @bfontaine's requested change? Thanks! |
|
No need to bother: spark 2.1.1 is released and this patch is included. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 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.
See apache/spark#16429
brew install --build-from-source <formula>, where<formula>is the name of the formula you're submitting?brew audit --strict <formula>(after doingbrew install <formula>)?