[Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?
Fri Jan 29 13:42:47 CST 2010
I'm a heavy user of scikits.timeseries so I am very interested in
having native datetime objects in Numpy. However, when I did play with
it about a week ago. I found inconsistencies between the actual code
and the NEP. The "Example of use" section mostly doesn't work. I
understand the need to put it out there so it gets used, but for the
moment I think potential users are still those who compile from the
dev. tree anyway.
Thanks for all the hard work that has been put into this,
On Thu, Jan 28, 2010 at 7:58 PM, David Cournapeau <email@example.com> wrote:
> Charles R Harris wrote:
>> On Thu, Jan 28, 2010 at 12:33 AM, David Cournapeau
>> <firstname.lastname@example.org <mailto:email@example.com>> wrote:
>> Because Travis was against it when it was suggested last september or
>> so. And removing in 1.4.x a feature introduced in 1.4.0 is weird.
>> But wasn't that decision based on the premiss that the datetime work
>> wouldn't break the ABI?
> Well, this and because Travis is the BFDL of NumPy as far as I am
> concerned :) So I think it should be his decision whether to remove it
> or not.
>> I don't see anything weird about making 1.4 work
>> with existing binaries.
> Indeed, but that's not really what I am saying :) I am saying there is a
> tradeoff between breaking people's code (for people using datetime) and
> keeping a compatible ABI.
> So the decision depends quite a bit on how many people use the datetime
>> If we are going to break the ABI, and it looks
>> like we will, then it would be better if the word went out early so that
>> projects that depend on numpy can be prepared for the change. So my
>> preference would be to remove the incompatibility in 1.4 and introduce
>> it in 1.5.
> Assuming not many people depend on datetime in 1.4.0, that would be my
> preference as well.
> NumPy-Discussion mailing list
More information about the NumPy-Discussion