[
https://issues.apache.org/jira/browse/SPARK-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179247#comment-15179247
]
Juliet Hougland commented on SPARK-13587:
-----------------------------------------
Currently the way users specify the workers' python interpreter is through the
PYSPARK_PYTHON env variable. It would be beneficial to users to allow that path
to be specified by a cli flag. That is a current rough edge of using already
installed envs on a cluster.
If this was added as a cli flag, I could see valid options being
'pyspark/python/path', 'venv' (temp virtualenv), and 'conda' (temp conda env)
and requiring a second flag to specify the requirements file. I think it helps
prevent an explosion of flag for spark submit while helping handle a very
important and often changed parameter for a job. What do you think of this?
> Support virtualenv in PySpark
> -----------------------------
>
> Key: SPARK-13587
> URL: https://issues.apache.org/jira/browse/SPARK-13587
> Project: Spark
> Issue Type: Improvement
> Components: PySpark
> Reporter: Jeff Zhang
>
> Currently, it's not easy for user to add third party python packages in
> pyspark.
> * One way is to using --py-files (suitable for simple dependency, but not
> suitable for complicated dependency, especially with transitive dependency)
> * Another way is install packages manually on each node (time wasting, and
> not easy to switch to different environment)
> Python has now 2 different virtualenv implementation. One is native
> virtualenv another is through conda. This jira is trying to migrate these 2
> tools to distributed environment
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
