[Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?
Thu Jan 28 01:33:18 CST 2010
Charles R Harris wrote:
> On Wed, Jan 27, 2010 at 11:39 PM, David Cournapeau
> <firstname.lastname@example.org <mailto:email@example.com>> wrote:
> Charles R Harris wrote:
> > On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau
> <firstname.lastname@example.org <mailto:email@example.com>
> > <mailto:firstname.lastname@example.org <mailto:email@example.com>>> wrote:
> > firstname.lastname@example.org <mailto:email@example.com>
> <mailto:firstname.lastname@example.org <mailto:email@example.com>> wrote:
> > > Can we/someone add a warning on the front page
> > > (maybe under news for numpy download) about
> incompatibility of the
> > > binaries on sourceforge of scipy <=0.7.1 with numpy 1.4.0 ?
> > It seems that it will be quite difficult to fix the issue without
> > removing something (I tried to use datetime as user types,
> but this
> > opened a can of worms), so I am (quite reluctantly ) coming
> to the
> > conclusion we should just bite the bullet and change the ABI
> number (so
> > that importing anything will fail instead of crashing randomly).
> > Something like numpy 220.127.116.11, which would just have a
> different ABI
> > number than 1.4.0, without anything else.
> > Why do you think it would be better to make this change in 1.4 rather
> > than 1.5?
> Because then any extension fails to import with a clear message instead
> of crashing as it does now. It does not matter much if you know the
> crash is coming from an incompatible ABI, but it does if you don't :)
> But why not remove the change?
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.
More information about the NumPy-Discussion