What do we think about the trade-offs of having a shared 2.7/3.x codebase going forward?
As Python3 adds more nontrivial features, keeping compatibility with 2.7 becomes more burdensome. Will there be a separate py2-numpy branch/repo at some point before ending support? On Apr 15, 2017 4:48 AM, "Julian Taylor" <jtaylor.deb...@googlemail.com> wrote: > On 15.04.2017 02:19, Charles R Harris wrote: > > Hi All, > > > > It may be early to discuss dropping support for Python 2.7, but there is > > a disturbance in the force that suggests that it might be worth looking > > forward to the year 2020 when Python itself will drop support for 2.7. > > There is also a website, http://www.python3statement.org > > <http://www.python3statement.org/>, where several projects in the > > scientific python stack have pledged to be Python 2.7 free by that > > date. Given that, a preliminary discussion of the subject might be > > interesting, if only to gather information of where the community > > currently stands. > > > > Chuck > > > > > > I am very against planning to drop it. > Numpy is the lowest part of the scipy stack so it is not our decision to > do so and we don't gain that much by doing so. > Lets discuss this in 3 years or when the distributions kick out > python2.7 (which won't happen before ~2022). There is no point doing so > now. > Also PyPy does not plan on dropping 2.7 by that time. > > Also before we even consider this we need to fix our python3 support. > This means getting the IO functions > (https://github.com/numpy/numpy/pull/4208) in order and adding a string > type that people are less reluctant to use than the 4 byte unicode we > currently offer. > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
