Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/21939
my PRB fork passed w/python3.5:
https://amplab.cs.berkeley.edu/jenkins/view/RISELab%20Infra/job/ubuntuSparkPRB/68
this increases my confidence for a python3.5 upgrade on the centos workers,
but i'd like to do a bit more testing (as well as reach out to the dev@ list
for feedback) before we pull the trigger...
next steps:
* i created a symlink for python3.4 -> python3.5 on my testing build node
and just launched another PRB to test and see that nothing weird happens
(https://amplab.cs.berkeley.edu/jenkins/view/RISELab%20Infra/job/ubuntuSparkPRB/69).
so far it looks good.
* issue created: https://issues.apache.org/jira/browse/SPARK-25079
* i created a PR for the impending 3.5 bump. it won't impact existing PRB
builds: https://github.com/apache/spark/pull/22061
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
