Setting the "savespace" property encourages Numeric to keep the results of calculations at smaller precisions. The error in the test has been fixed by removing the test for now. It appears the result of the test is platform-dependent. There is a list of fixed and open bugs on the project page http://sourceforge.net/projects/numpy.

-----Original Message----- From: numpy-discussion-admin@lists.sourceforge.net [mailto:numpy-discussion-admin@lists.sourceforge.net]On Behalf Of Pete Shinners Sent: Saturday, July 08, 2000 12:36 AM To: numpy-discussion@sourceforge.net Subject: [Numpy-discussion] savebit questions and errors

i'm developing with some Numeric stuff and don't have a solid grasp on what the 'SAVEBIT' stuff is. it's not mentioned in the docs at all.

what's also strange is the the numpy testing "test_all.py" fails in the final sections when testing the savebit stuff.

can someone give a quicky description of what this flag can be used for?

also... i assume someone already knows about the error in the testing? i ran it on both a MIPS5000 IRIX system and an x86 win98 system and it errored out consistently on the test line 506.

_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/numpy-discussion