[Important for PySpark Devs]: Master now tests with Python 2.7 rather than 2.6 - please retest any Python PRs

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Important for PySpark Devs]: Master now tests with Python 2.7 rather than 2.6 - please retest any Python PRs

Holden Karau
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 : <a href="tel:(425)%20233-8271" value="+14252338271" target="_blank">425-233-8271
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Important for PySpark Devs]: Master now tests with Python 2.7 rather than 2.6 - please retest any Python PRs

Hyukjin Kwon
Thank you for informing this.

On 30 Mar 2017 3:52 a.m., "Holden Karau" <[hidden email]> 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 : <a href="tel:(425)%20233-8271" value="+14252338271" target="_blank">425-233-8271
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Important for PySpark Devs]: Master now tests with Python 2.7 rather than 2.6 - please retest any Python PRs

Jeff Zhang

Thanks, retrigger serveral pyspark PRs



Hyukjin Kwon <[hidden email]>于2017年3月30日周四 上午7:42写道:
Thank you for informing this.

On 30 Mar 2017 3:52 a.m., "Holden Karau" <[hidden email]> 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 : <a href="tel:(425)%20233-8271" value="+14252338271" class="gmail_msg" target="_blank">425-233-8271
Loading...