Re: [VOTE] Deprecate support for Python <3.6

2018-10-05 Thread Maxime Beauchemin
Today I merged the py3 deprecation PR!
https://github.com/apache/incubator-superset/pull/5985

On Tue, Sep 25, 2018 at 1:33 AM yongjie zhao  wrote:

> +1
>
> On Tue, Sep 25, 2018 at 1:53 AM Jim Jagielski  wrote:
>
> > It might also be good to bring up this discussion on users@, to gauge
> the
> > user community's take.
> >
> > > On Sep 21, 2018, at 12:51 AM, Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> > >
> > > Since Superset is a product, and not a library, people have the luxury
> to
> > > pick which version of Python they desire when setting up Superset.
> > >
> > > Supporting 2.7 has been a burden and we have to look into the future.
> > >
> > > Arguments for this:
> > > * take advantage of py2.7...py3.6 features
> > >   * type annotations
> > >   * async / await
> > >   * fstrings syntactic sugar
> > >   * a decade of improvements listed here:
> > > https://docs.python.org/3/whatsnew/index.html
> > > * less Superset bugs related to version incompatibilities
> > > * free up slots in the build matrix
> > > * faster
> > > * maintained beyond 2020
> > >
> > > Cons:
> > > * People living in the past will have to update their deploy scripts
> now
> > > instead of a year from now
> > >
> > > -
> > > if you "-1" please state your reasons!
> >
> >
>


Re: [VOTE] Deprecate support for Python <3.6

2018-09-24 Thread yongjie zhao
+1

On Tue, Sep 25, 2018 at 1:53 AM Jim Jagielski  wrote:

> It might also be good to bring up this discussion on users@, to gauge the
> user community's take.
>
> > On Sep 21, 2018, at 12:51 AM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >
> > Since Superset is a product, and not a library, people have the luxury to
> > pick which version of Python they desire when setting up Superset.
> >
> > Supporting 2.7 has been a burden and we have to look into the future.
> >
> > Arguments for this:
> > * take advantage of py2.7...py3.6 features
> >   * type annotations
> >   * async / await
> >   * fstrings syntactic sugar
> >   * a decade of improvements listed here:
> > https://docs.python.org/3/whatsnew/index.html
> > * less Superset bugs related to version incompatibilities
> > * free up slots in the build matrix
> > * faster
> > * maintained beyond 2020
> >
> > Cons:
> > * People living in the past will have to update their deploy scripts now
> > instead of a year from now
> >
> > -
> > if you "-1" please state your reasons!
>
>


Re: [VOTE] Deprecate support for Python <3.6

2018-09-24 Thread Jim Jagielski
It might also be good to bring up this discussion on users@, to gauge the user 
community's take.

> On Sep 21, 2018, at 12:51 AM, Maxime Beauchemin  
> wrote:
> 
> Since Superset is a product, and not a library, people have the luxury to
> pick which version of Python they desire when setting up Superset.
> 
> Supporting 2.7 has been a burden and we have to look into the future.
> 
> Arguments for this:
> * take advantage of py2.7...py3.6 features
>   * type annotations
>   * async / await
>   * fstrings syntactic sugar
>   * a decade of improvements listed here:
> https://docs.python.org/3/whatsnew/index.html
> * less Superset bugs related to version incompatibilities
> * free up slots in the build matrix
> * faster
> * maintained beyond 2020
> 
> Cons:
> * People living in the past will have to update their deploy scripts now
> instead of a year from now
> 
> -
> if you "-1" please state your reasons!



Re: [VOTE] Deprecate support for Python <3.6

2018-09-23 Thread Nishant Bangarwa
+1

--
Nishant Bangarwa

Hortonworks

On 9/21/18, 12:03 PM, "Arthur Wiedmer"  wrote:

+1 (non binding)

On Thu, Sep 20, 2018, 21:51 Maxime Beauchemin 
wrote:

> Since Superset is a product, and not a library, people have the luxury to
> pick which version of Python they desire when setting up Superset.
>
> Supporting 2.7 has been a burden and we have to look into the future.
>
> Arguments for this:
> * take advantage of py2.7...py3.6 features
>* type annotations
>* async / await
>* fstrings syntactic sugar
>* a decade of improvements listed here:
> https://docs.python.org/3/whatsnew/index.html
> * less Superset bugs related to version incompatibilities
> * free up slots in the build matrix
> * faster
> * maintained beyond 2020
>
> Cons:
> * People living in the past will have to update their deploy scripts now
> instead of a year from now
>
> -
> if you "-1" please state your reasons!
>




Re: [VOTE] Deprecate support for Python <3.6

2018-09-20 Thread Timi Fasubaa
+1
On Fri, Sep 21, 2018 at 12:29 AM Eli Brumbaugh
 wrote:

> +1
> On Thu, Sep 20, 2018 at 10:16 PM John Bodley 
> wrote:
>
> > +1
> >
> > > On Sep 20, 2018, at 9:51 PM, Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> > >
> > > Since Superset is a product, and not a library, people have the luxury
> to
> > > pick which version of Python they desire when setting up Superset.
> > >
> > > Supporting 2.7 has been a burden and we have to look into the future.
> > >
> > > Arguments for this:
> > > * take advantage of py2.7...py3.6 features
> > >   * type annotations
> > >   * async / await
> > >   * fstrings syntactic sugar
> > >   * a decade of improvements listed here:
> > > https://docs.python.org/3/whatsnew/index.html
> > > * less Superset bugs related to version incompatibilities
> > > * free up slots in the build matrix
> > > * faster
> > > * maintained beyond 2020
> > >
> > > Cons:
> > > * People living in the past will have to update their deploy scripts
> now
> > > instead of a year from now
> > >
> > > -
> > > if you "-1" please state your reasons!
> >
> --
> Eli Sebastian Brumbaugh
> Design Lead  |  Data Platform  |  Data UX
> Indigenous@ Diversity Group Founder
>


Re: [VOTE] Deprecate support for Python <3.6

2018-09-20 Thread Eli Brumbaugh
+1
On Thu, Sep 20, 2018 at 10:16 PM John Bodley  wrote:

> +1
>
> > On Sep 20, 2018, at 9:51 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >
> > Since Superset is a product, and not a library, people have the luxury to
> > pick which version of Python they desire when setting up Superset.
> >
> > Supporting 2.7 has been a burden and we have to look into the future.
> >
> > Arguments for this:
> > * take advantage of py2.7...py3.6 features
> >   * type annotations
> >   * async / await
> >   * fstrings syntactic sugar
> >   * a decade of improvements listed here:
> > https://docs.python.org/3/whatsnew/index.html
> > * less Superset bugs related to version incompatibilities
> > * free up slots in the build matrix
> > * faster
> > * maintained beyond 2020
> >
> > Cons:
> > * People living in the past will have to update their deploy scripts now
> > instead of a year from now
> >
> > -
> > if you "-1" please state your reasons!
>
-- 
Eli Sebastian Brumbaugh
Design Lead  |  Data Platform  |  Data UX
Indigenous@ Diversity Group Founder


Re: [VOTE] Deprecate support for Python <3.6

2018-09-20 Thread John Bodley
+1

> On Sep 20, 2018, at 9:51 PM, Maxime Beauchemin  
> wrote:
> 
> Since Superset is a product, and not a library, people have the luxury to
> pick which version of Python they desire when setting up Superset.
> 
> Supporting 2.7 has been a burden and we have to look into the future.
> 
> Arguments for this:
> * take advantage of py2.7...py3.6 features
>   * type annotations
>   * async / await
>   * fstrings syntactic sugar
>   * a decade of improvements listed here:
> https://docs.python.org/3/whatsnew/index.html
> * less Superset bugs related to version incompatibilities
> * free up slots in the build matrix
> * faster
> * maintained beyond 2020
> 
> Cons:
> * People living in the past will have to update their deploy scripts now
> instead of a year from now
> 
> -
> if you "-1" please state your reasons!


[VOTE] Deprecate support for Python <3.6

2018-09-20 Thread Maxime Beauchemin
Since Superset is a product, and not a library, people have the luxury to
pick which version of Python they desire when setting up Superset.

Supporting 2.7 has been a burden and we have to look into the future.

Arguments for this:
* take advantage of py2.7...py3.6 features
   * type annotations
   * async / await
   * fstrings syntactic sugar
   * a decade of improvements listed here:
https://docs.python.org/3/whatsnew/index.html
* less Superset bugs related to version incompatibilities
* free up slots in the build matrix
* faster
* maintained beyond 2020

Cons:
* People living in the past will have to update their deploy scripts now
instead of a year from now

-
if you "-1" please state your reasons!