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

pyspark: 2.3.2 -> 2.4.0, fix version bounds #54898

Merged
merged 1 commit into from Jan 30, 2019

Conversation

Projects
None yet
3 participants
@matthewbauer
Copy link
Member

commented Jan 29, 2019

py4j seems to work fine with this version

};

# pypandoc is broken with pandoc2, so we just lose docs.
postPatch = ''
sed -i "s/'pypandoc'//" setup.py
# Current release works fine with py4j 0.10.8.1
substituteInPlace setup.py --replace py4j==0.10.7 py4j==0.10.8.1

This comment has been minimized.

Copy link
@dotlambda

dotlambda Jan 29, 2019

Member

Wouldn't it make sense to specify something like py4j>=0.10.7,<0.11?

This comment has been minimized.

Copy link
@matthewbauer

matthewbauer Jan 30, 2019

Author Member

Done

pyspark: 2.3.2 -> 2.4.0, fix version bounds
py4j seems to work fine with this version

@matthewbauer matthewbauer force-pushed the matthewbauer:pyspark-fix branch from 98acf77 to c0f8270 Jan 30, 2019

@matthewbauer matthewbauer merged commit bdc7aab into NixOS:master Jan 30, 2019

1 check was pending

grahamcofborg-eval Cloning project
Details

@matthewbauer matthewbauer deleted the matthewbauer:pyspark-fix branch Feb 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.