+1 I'd like to point out that one of our dependencies, scikit, already dropped support for python 2. If more dependencies drop support before 1.1.20, we might start running into further issues like we already did. As part of that decision, I'd propose to see what the detailed timelines of our dependencies are and then adjust our timeline accordingly.
-Marco Pedro Larroy <pedro.larroy.li...@gmail.com> schrieb am Mi., 15. Mai 2019, 00:15: > +1 Let python2 rest, let's simplify our infrastructure and need to > support old Python versions. > > On Mon, May 13, 2019 at 1:58 PM Jake Lee <gstu1...@gmail.com> wrote: > > > > +1 Recently I upgraded the Numpy version and found out that Pylint had > > false alarm on it. The Pylint fix is only available on Python3. So I > > changed the default python version of 'make pylint' command to python3 > (PR > > haven't been merged). It's time to drop support for Python2. > > > > On Mon, May 13, 2019 at 1:37 PM Junru Shao <junrushao1...@gmail.com> > wrote: > > > > > +1 > > > > > > On Mon, May 13, 2019 at 1:34 PM Aaron Markham < > aaron.s.mark...@gmail.com> > > > wrote: > > > > > > > +1 for the pledge and to start moving things to Python 3. > > > > I think our installation instructions and tutorials can be updated to > > > > default to Python3 and we should update Python2-only tutorials. I > know > > > > we have a handful of those, and when I spot them, I'll create an > > > > issue. > > > > I can also look at migrating the docs build to Python 3. > > > > Should we add a new label for issues relating to migrating to > Python3? > > > > Cheers, > > > > Aaron > > > > > > > > On Mon, May 13, 2019 at 12:04 PM Zach Kimberg < > zachary.kimb...@gmail.com > > > > > > > > wrote: > > > > > > > > > > Right now, the official date for ending support for Python 2.7 > (and all > > > > of > > > > > python2) is set to January 1 [1]. As part of it, a number of > projects > > > > have > > > > > pledged to drop support for Python2 in or before 2020 including > > > > Tensorflow, > > > > > requests, pandas, ipython, numpy, pillow, and Cython [2]. I > believe we > > > > > should also join in this pledge on python3statement.org [2] > because it > > > > > would help clean up our project and it would be difficult to > continue > > > > > supporting Python2 anyway when some of our dependencies are > dropping > > > > > support. > > > > > > > > > > As a concrete step, we should decide on a date to remove all > usages of > > > > > Python2 from our CI and consider that officially dropping support. > > > > > Following that, we can expect PRs will end up breaking support for > > > > Python2. > > > > > I suggest just using the same date that Python is dropping support > of > > > > > January 1. We may also need to update some examples or scripts that > > > were > > > > > written only for python2 that are around the project. Any thoughts? > > > > > > > > > > Zach > > > > > > > > > > > > > > > [1] - https://www.python.org/dev/peps/pep-0373/ > > > > > [2] - https://python3statement.org/ > > > > > > > >
