On Fri, 14 Apr 2017 22:19:42 -0700
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, but the most important.) What I mean
> is: if we dropped 2.7 suppo
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
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
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
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
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,
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,
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
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,
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
> > disturbance in the force that suggests that it might be worth looking
> > forw
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
> 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
>
11 matches
Mail list logo
