Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Ralf Gommers
On Sat, Apr 15, 2017 at 7:02 PM, Nathaniel Smith wrote: > On Fri, Apr 14, 2017 at 10:47 PM, Ralf Gommers > wrote: > > > > > > On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: > [...] > >> From numpy's perspective, I feel like the most important reason to > >> continue supporting 2.7 is o

[Numpy-discussion] testing needed for f2py with char/string arrays

2017-04-15 Thread Julian Taylor
hi, we need to deprecate the NPY_CHAR typenumber [0] in order to enable us to add new core dtypes without adding ugly hacks to our ABI. Technically the typenumber was deprecated way back in 1.6 when it accidentally broke our ABI. But due to lack of time f2py never got updated to actually follow thr

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Charles R Harris
On Fri, Apr 14, 2017 at 11:47 PM, Ralf Gommers wrote: > > > On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: > >> On Fri, Apr 14, 2017 at 5:19 PM, Charles R Harris >> wrote: >> > Hi All, >> > >> > It may be early to discuss dropping support for Python 2.7, but there >> is a >> > disturba

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Julian Taylor
On 15.04.2017 16:30, Julian Taylor wrote: > On 15.04.2017 16:17, Marten van Kerkwijk wrote: >> Hi All, >> >> I think Nathaniel had a good summary. My own 2¢ are mostly about the >> burden of supporting python2. I have only recently attempted to make >> changes in the C codebase of numpy and one of

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Julian Taylor
On 15.04.2017 16:17, Marten van Kerkwijk wrote: > Hi All, > > I think Nathaniel had a good summary. My own 2¢ are mostly about the > burden of supporting python2. I have only recently attempted to make > changes in the C codebase of numpy and one of the reasons I found this > more than a little da

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Marten van Kerkwijk
Hi All, I think Nathaniel had a good summary. My own 2¢ are mostly about the burden of supporting python2. I have only recently attempted to make changes in the C codebase of numpy and one of the reasons I found this more than a little daunting is the complex web of include files. In this respect,

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread CJ Carey
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,

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Julian Taylor
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 w

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

2017-04-15 Thread Nathaniel Smith
On Fri, Apr 14, 2017 at 10:47 PM, Ralf Gommers wrote: > > > On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: [...] >> From numpy's perspective, I feel like the most important reason to >> continue supporting 2.7 is our ability to convince people to keep >> upgrading. (Not the only reason,