[Numpy-discussion] failure building trunk with mingw
Sun Nov 22 09:25:32 CST 2009
On Mon, Nov 23, 2009 at 12:14 AM, <email@example.com> wrote:
> On Sun, Nov 22, 2009 at 10:01 AM, David Cournapeau <firstname.lastname@example.org> wrote:
>> On Sun, Nov 22, 2009 at 11:45 PM, Charles R Harris
>> <email@example.com> wrote:
>>> Might be nice to print out the actual values of np.spacing and np.nextafter
>> Yes, I should add some utilities to print those for this kind of test.
>> But in this case, I know the problem: mingw gcc use 80 bits long
>> double but it uses the MS runtime which considers double and long
>> double to be the same (8 bytes).
>> I think the real fix is to force npy_longdouble to be double on mingw,
>> but I don't want to make that change now for 1.4.0.
> adding the failing type in the test to the failure message would also
> be helpful
Yes, you're right. I also used the nose facility for using generators
for complex corner cases, but with retrospect, it is not so useful,
because you don't get a name when you have a failure (or maybe I am
using it wrong).
More information about the NumPy-Discussion