Re: [VOTE] Deprecate support for Python <3.6
+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
+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
+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
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: ASF project maturity model
Started filling int he checklist here: https://github.com/apache/incubator-superset/issues/5951 On Thu, Sep 20, 2018 at 5:15 PM Maxime Beauchemin < maximebeauche...@gmail.com> wrote: > Justin, > > It seems to me like the maturity model doc goes beyond what's required for > graduation. Quoting the doc: > > "It might be useful for top-level ASF projects to regularly assess > their maturity based on this model, but this is not a requirement at this > time." > It seems to imply that top-level project are not expected to check all > those boxes. > > We've been operating by this guide > https://incubator.apache.org/guides/graduation.html > > Looking at the checklist, it seemed to me like the main missing items are > around sorting out dependency licenses and getting to a steady release > process with conforming releases. > > Max > > On Thu, Sep 20, 2018 at 3:39 PM Justin Mclean wrote: > >> Hi, >> >> It might be useful for the project to fill in [1] and see what they would >> need to do in order to get to a state where the project could be considered >> for graduation. Currently, and I could be wrong, I think this project has a >> long way to go and it may not realise that. While this is not a >> requirement for graduation many projects fill it out and it can be quite >> helpful. >> >> Thinks, >> Justin >> >> 1. >> https://community.apache.org/apache-way/apache-project-maturity-model.html >> >
Re: ASF project maturity model
Justin, It seems to me like the maturity model doc goes beyond what's required for graduation. Quoting the doc: > "It might be useful for top-level ASF projects to regularly assess their maturity based on this model, but this is not a requirement at this time." It seems to imply that top-level project are not expected to check all those boxes. We've been operating by this guide https://incubator.apache.org/guides/graduation.html Looking at the checklist, it seemed to me like the main missing items are around sorting out dependency licenses and getting to a steady release process with conforming releases. Max On Thu, Sep 20, 2018 at 3:39 PM Justin Mclean wrote: > Hi, > > It might be useful for the project to fill in [1] and see what they would > need to do in order to get to a state where the project could be considered > for graduation. Currently, and I could be wrong, I think this project has a > long way to go and it may not realise that. While this is not a > requirement for graduation many projects fill it out and it can be quite > helpful. > > Thinks, > Justin > > 1. > https://community.apache.org/apache-way/apache-project-maturity-model.html >
ASF project maturity model
Hi, It might be useful for the project to fill in [1] and see what they would need to do in order to get to a state where the project could be considered for graduation. Currently, and I could be wrong, I think this project has a long way to go and it may not realise that. While this is not a requirement for graduation many projects fill it out and it can be quite helpful. Thinks, Justin 1. https://community.apache.org/apache-way/apache-project-maturity-model.html
