You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spark.apache.org by Holden Karau <ho...@pigscanfly.ca> on 2017/03/29 18:52:20 UTC
[Important for PySpark Devs]: Master now tests with Python 2.7 rather
than 2.6 - please retest any Python PRs
Hi PySpark Developers,
In https://issues.apache.org/jira/browse/SPARK-19955 /
https://github.com/apache/spark/pull/17355, as part of our continued Python
2.6 deprecation https://issues.apache.org/jira/browse/SPARK-15902 &
eventual removal https://issues.apache.org/jira/browse/SPARK-12661 ,
Jenkins master will now test with Python 2.7 rather than Python 2.6. If you
have a pending Python PR please re-run Jenkins tests prior to merge to
avoid issues.
For your local testing *make sure you have a version of Python 2.7
installed on your machine *otherwise it will default to using the python
executable and in the future you may run into compatibility issues.
Note: this only impacts master and has not been merged to other branches,
so if you want to make fixes that are planned for back ported to 2.1,
please continue to use 2.6 compatible Python code (and note you can always
explicitly set a python version to be run with the --python-executables
flag when testing locally).
Cheers,
Holden :)
P.S.
If you run int any issues around this please feel free (as always) to reach
out and ping me.
--
Cell : 425-233-8271 <(425)%20233-8271>
Twitter: https://twitter.com/holdenkarau
Re: [Important for PySpark Devs]: Master now tests with Python 2.7
rather than 2.6 - please retest any Python PRs
Posted by Jeff Zhang <zj...@gmail.com>.
Thanks, retrigger serveral pyspark PRs
Hyukjin Kwon <gu...@gmail.com>于2017年3月30日周四 上午7:42写道：
> Thank you for informing this.
>
> On 30 Mar 2017 3:52 a.m., "Holden Karau" <ho...@pigscanfly.ca> wrote:
>
> Hi PySpark Developers,
>
> In https://issues.apache.org/jira/browse/SPARK-19955 /
> https://github.com/apache/spark/pull/17355, as part of our continued
> Python 2.6 deprecation https://issues.apache.org/jira/browse/SPARK-15902
> & eventual removal https://issues.apache.org/jira/browse/SPARK-12661 ,
> Jenkins master will now test with Python 2.7 rather than Python 2.6. If you
> have a pending Python PR please re-run Jenkins tests prior to merge to
> avoid issues.
>
> For your local testing *make sure you have a version of Python 2.7
> installed on your machine *otherwise it will default to using the python
> executable and in the future you may run into compatibility issues.
>
> Note: this only impacts master and has not been merged to other branches,
> so if you want to make fixes that are planned for back ported to 2.1,
> please continue to use 2.6 compatible Python code (and note you can always
> explicitly set a python version to be run with the --python-executables
> flag when testing locally).
>
> Cheers,
>
> Holden :)
>
> P.S.
>
> If you run int any issues around this please feel free (as always) to
> reach out and ping me.
>
> --
> Cell : 425-233-8271 <(425)%20233-8271>
> Twitter: https://twitter.com/holdenkarau
>
>
Re: [Important for PySpark Devs]: Master now tests with Python 2.7
rather than 2.6 - please retest any Python PRs
Posted by Hyukjin Kwon <gu...@gmail.com>.
Thank you for informing this.
On 30 Mar 2017 3:52 a.m., "Holden Karau" <ho...@pigscanfly.ca> wrote:
> Hi PySpark Developers,
>
> In https://issues.apache.org/jira/browse/SPARK-19955 /
> https://github.com/apache/spark/pull/17355, as part of our continued
> Python 2.6 deprecation https://issues.apache.org/jira/browse/SPARK-15902
> & eventual removal https://issues.apache.org/jira/browse/SPARK-12661 ,
> Jenkins master will now test with Python 2.7 rather than Python 2.6. If you
> have a pending Python PR please re-run Jenkins tests prior to merge to
> avoid issues.
>
> For your local testing *make sure you have a version of Python 2.7
> installed on your machine *otherwise it will default to using the python
> executable and in the future you may run into compatibility issues.
>
> Note: this only impacts master and has not been merged to other branches,
> so if you want to make fixes that are planned for back ported to 2.1,
> please continue to use 2.6 compatible Python code (and note you can always
> explicitly set a python version to be run with the --python-executables
> flag when testing locally).
>
> Cheers,
>
> Holden :)
>
> P.S.
>
> If you run int any issues around this please feel free (as always) to
> reach out and ping me.
>
> --
> Cell : 425-233-8271 <(425)%20233-8271>
> Twitter: https://twitter.com/holdenkarau
>