so... i've updated the python testing framework to run on python 3.6, and
drop support for testing against python 2.7 (and pypy 2.5.1).
https://github.com/apache/spark/pull/26330
anyways: this is ready to merge, but i'm more than happy to hold off for
the time being if we're still a little shy
i'm currently testing PyPy3.6 v7.2.0 w/this pull request:
https://github.com/apache/spark/pull/26330
On Wed, Oct 30, 2019 at 2:31 PM Maciej Szymkiewicz
wrote:
> Could we upgrade to PyPy3.6 v7.2.0?
> On 10/30/19 9:45 PM, Shane Knapp wrote:
>
> one quick thing: we currently test against python2.7
+1
On Thu, Oct 31, 2019 at 11:21 AM Bryan Cutler wrote:
> +1 for deprecating
>
> On Wed, Oct 30, 2019 at 2:46 PM Shane Knapp wrote:
>
>> sure. that shouldn't be too hard, but we've historically given very
>> little support to it.
>>
>> On Wed, Oct 30, 2019 at 2:31 PM Maciej Szymkiewicz <
>> ms
+1 for deprecating
On Wed, Oct 30, 2019 at 2:46 PM Shane Knapp wrote:
> sure. that shouldn't be too hard, but we've historically given very
> little support to it.
>
> On Wed, Oct 30, 2019 at 2:31 PM Maciej Szymkiewicz
> wrote:
>
>> Could we upgrade to PyPy3.6 v7.2.0?
>> On 10/30/19 9:45 PM, S
sure. that shouldn't be too hard, but we've historically given very little
support to it.
On Wed, Oct 30, 2019 at 2:31 PM Maciej Szymkiewicz
wrote:
> Could we upgrade to PyPy3.6 v7.2.0?
> On 10/30/19 9:45 PM, Shane Knapp wrote:
>
> one quick thing: we currently test against python2.7, 3.6 *and
Could we upgrade to PyPy3.6 v7.2.0?
On 10/30/19 9:45 PM, Shane Knapp wrote:
> one quick thing: we currently test against python2.7, 3.6 *and*
> pypy2.5.1 (python2.7).
>
> what are our plans for pypy?
>
>
> On Wed, Oct 30, 2019 at 12:26 PM Dongjoon Hyun
> mailto:dongjoon.h...@gmail.com>> wrote:
>
also, here's my PR for dropping 2.7 tests:
https://github.com/apache/spark/pull/26330
On Wed, Oct 30, 2019 at 1:45 PM Shane Knapp wrote:
> one quick thing: we currently test against python2.7, 3.6 *and* pypy2.5.1
> (python2.7).
>
> what are our plans for pypy?
>
>
> On Wed, Oct 30, 2019 at 12:2
one quick thing: we currently test against python2.7, 3.6 *and* pypy2.5.1
(python2.7).
what are our plans for pypy?
On Wed, Oct 30, 2019 at 12:26 PM Dongjoon Hyun
wrote:
> Thank you all. I made a PR for that.
>
> https://github.com/apache/spark/pull/26326
>
> On Tue, Oct 29, 2019 at 5:45 AM T
Thank you all. I made a PR for that.
https://github.com/apache/spark/pull/26326
On Tue, Oct 29, 2019 at 5:45 AM Takeshi Yamamuro
wrote:
> +1, too.
>
> On Tue, Oct 29, 2019 at 4:16 PM Holden Karau wrote:
>
>> +1 to deprecating but not yet removing support for 3.6
>>
>> On Tue, Oct 29, 2019 at 3
+1, too.
On Tue, Oct 29, 2019 at 4:16 PM Holden Karau wrote:
> +1 to deprecating but not yet removing support for 3.6
>
> On Tue, Oct 29, 2019 at 3:47 AM Shane Knapp wrote:
>
>> +1 to testing the absolute minimum number of python variants as
>> possible. ;)
>>
>> On Mon, Oct 28, 2019 at 7:46 P
+1 to deprecating but not yet removing support for 3.6
On Tue, Oct 29, 2019 at 3:47 AM Shane Knapp wrote:
> +1 to testing the absolute minimum number of python variants as possible.
> ;)
>
> On Mon, Oct 28, 2019 at 7:46 PM Hyukjin Kwon wrote:
>
>> +1 from me as well.
>>
>> 2019년 10월 29일 (화) 오전
+1 to testing the absolute minimum number of python variants as possible.
;)
On Mon, Oct 28, 2019 at 7:46 PM Hyukjin Kwon wrote:
> +1 from me as well.
>
> 2019년 10월 29일 (화) 오전 5:34, Xiangrui Meng 님이 작성:
>
>> +1. And we should start testing 3.7 and maybe 3.8 in Jenkins.
>>
>> On Thu, Oct 24, 2019
+1 from me as well.
2019년 10월 29일 (화) 오전 5:34, Xiangrui Meng 님이 작성:
> +1. And we should start testing 3.7 and maybe 3.8 in Jenkins.
>
> On Thu, Oct 24, 2019 at 9:34 AM Dongjoon Hyun
> wrote:
>
>> Thank you for starting the thread.
>>
>> In addition to that, we currently are testing Python 3.6 on
+1. And we should start testing 3.7 and maybe 3.8 in Jenkins.
On Thu, Oct 24, 2019 at 9:34 AM Dongjoon Hyun
wrote:
> Thank you for starting the thread.
>
> In addition to that, we currently are testing Python 3.6 only in Apache
> Spark Jenkins environment.
>
> Given that Python 3.8 is already ou
Thank you for starting the thread.
In addition to that, we currently are testing Python 3.6 only in Apache
Spark Jenkins environment.
Given that Python 3.8 is already out and Apache Spark 3.0.0 RC1 will start
next January
(https://spark.apache.org/versioning-policy.html), I'm +1 for the
deprecati
15 matches
Mail list logo