> On Dec 4, 2015, at 9:49 AM, Charles R Harris
> wrote:
>
>
>
> On Fri, Dec 4, 2015 at 2:40 AM, Julian Taylor
> wrote:
> dropping 3.2: +-0 as it would remove some extra code in our broken py3
> string handling but not much
> dropping 3.3: -1 doesn't gain us anything so far I know
> droppi
On Fri, Dec 4, 2015 at 2:40 AM, Julian Taylor wrote:
> dropping 3.2: +-0 as it would remove some extra code in our broken py3
> string handling but not much
> dropping 3.3: -1 doesn't gain us anything so far I know
> dropping 2.6: -1, I don't see not enough advantage the only issue I know
> of is
On Fri, Dec 4, 2015 at 6:13 AM, David Cournapeau wrote:
>
>
> On Fri, Dec 4, 2015 at 11:06 AM, Nathaniel Smith wrote:
>
>> On Fri, Dec 4, 2015 at 1:27 AM, David Cournapeau
>> wrote:
>> > I would be in favour of dropping 3.3, but not 2.6 until it becomes too
>> > cumbersome to support.
>> >
>> >
On Fri, Dec 4, 2015 at 11:06 AM, Nathaniel Smith wrote:
> On Fri, Dec 4, 2015 at 1:27 AM, David Cournapeau
> wrote:
> > I would be in favour of dropping 3.3, but not 2.6 until it becomes too
> > cumbersome to support.
> >
> > As a data point, as of april, 2.6 was more downloaded than all python
On Fri, Dec 4, 2015 at 1:27 AM, David Cournapeau wrote:
> I would be in favour of dropping 3.3, but not 2.6 until it becomes too
> cumbersome to support.
>
> As a data point, as of april, 2.6 was more downloaded than all python 3.X
> versions together when looking at pypi numbers:
> https://carema
On 03/12/15 22:07, David Verelst wrote:
Can this workflow be incorporated into |setuptools|/|numpy.distutils|?
Something along the lines as:
Take a look at what SciPy does.
https://github.com/scipy/scipy/blob/81c096001974f0b5efe29ec83b54f725cc681540/scipy/fftpack/setup.py
Multiple Fortran fi
On 03/12/15 22:38, Eric Firing wrote:
Right, but for each function that requires writing two wrappers, one in
Fortran and a second one in cython.
Yes, you need two wrappers for each function, one in Cython and one in
Fortran 2003. That is what fwrap is supposed to automate, but it has
been a
dropping 3.2: +-0 as it would remove some extra code in our broken py3
string handling but not much
dropping 3.3: -1 doesn't gain us anything so far I know
dropping 2.6: -1, I don't see not enough advantage the only issue I know
of is an occasional set literal which gets caught by our test-suite
im
I would be in favour of dropping 3.3, but not 2.6 until it becomes too
cumbersome to support.
As a data point, as of april, 2.6 was more downloaded than all python 3.X
versions together when looking at pypi numbers:
https://caremad.io/2015/04/a-year-of-pypi-downloads/
David
On Thu, Dec 3, 2015 a
