Github user shaneknapp commented on the issue:
https://github.com/apache/spark/pull/22061
@BryanCutler the reason i'm not doing the upgrade is that the path for the
current py3.4 anaconda env is hard-coded in to the python test running code
across all branches.
this means if i do the upgrade to 3.5 on the workers and create the
symlink, all branches will be running 3.5 w/only a small amount of testing.
also, i'll need to ensure that there are no package/dependency issues
w/previously installed libs.
if i create a new anaconda 3.5 env, then i will need to immediately change
the path in dev/run-tests.py for whatever branch(es) that we want 3.5... as
well as hack on the conda package definitions so that i can ansibileize things.
it's a bit more work that i think you might expect... i'll be working on
getting this sorted this week.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
