[ 
https://issues.apache.org/jira/browse/SPARK-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218109#comment-15218109
 ] 

Mike Sukmanowsky commented on SPARK-13587:
------------------------------------------

The NFS is a good idea for a current workaround. It's still a pain to build all 
required eggs in a dependency file like requirements.txt unless pyspark 
supports something like .pex files which build a self-contained python 
executable from said requirements file.

If pex files were supported by pyspark, the daemon + workers would simply use 
/path/to/file.pex as the Python executable and get a fully baked virtualenv for 
free without Spark needing to concern itself with building these files.

Twitter has reportedly used this to ship distributed Python applications for 
sometime.

> Support virtualenv in PySpark
> -----------------------------
>
>                 Key: SPARK-13587
>                 URL: https://issues.apache.org/jira/browse/SPARK-13587
>             Project: Spark
>          Issue Type: New Feature
>          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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to