You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:16:20 UTC
[jira] [Resolved] (SPARK-6883) Fork pyspark's cloudpickle as a
separate dependency
[ https://issues.apache.org/jira/browse/SPARK-6883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-6883.
---------------------------------
Resolution: Incomplete
> Fork pyspark's cloudpickle as a separate dependency
> ---------------------------------------------------
>
> Key: SPARK-6883
> URL: https://issues.apache.org/jira/browse/SPARK-6883
> Project: Spark
> Issue Type: Improvement
> Components: PySpark
> Reporter: Kyle Kelley
> Priority: Major
> Labels: bulk-closed, fork
>
> IPython, pyspark, picloud/multyvac/cloudpipe all rely on cloudpickle from various sources (cloud, pyspark, and multyvac correspondingly). It would be great to have this as a separately maintained project that can:
> * Work with Python3
> * Add tests!
> * Use higher order pickling (when on Python3)
> * Be installed with pip
> We're starting this off at the PyCon sprints under https://github.com/cloudpipe/cloudpickle. We'd like to coordinate with PySpark to make it work across all the above mentioned projects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org