Re: [Numpy-discussion] printoption to allow hexified floats?

2010-12-02 Thread Ken Basye
Thanks for the replies. Robert is right; many numerical operations, particularly complex ones, generate different values across platforms, and we deal with these by storing the values from some platform as a reference and using allclose(), which requires extra work. But many basic operations

Re: [Numpy-discussion] printoption to allow hexified floats?

2010-12-02 Thread Benjamin Root
On Thu, Dec 2, 2010 at 11:17 AM, Ken Basye kbas...@jhu.edu wrote: Thanks for the replies. Robert is right; many numerical operations, particularly complex ones, generate different values across platforms, and we deal with these by storing the values from some platform as a reference and

[Numpy-discussion] printoption to allow hexified floats?

2010-12-01 Thread Ken Basye
Hi Numpy folks, When working with floats, I prefer to have exact string representations in doctests and other reference-based testing; I find it helps a lot to avoid chasing cross-platform differences that are really about the string conversion rather than about numerical differences.

Re: [Numpy-discussion] printoption to allow hexified floats?

2010-12-01 Thread David Warde-Farley
On 2010-12-01, at 2:18 PM, Ken Basye wrote: On a somewhat related note, is there a table someplace which shows which versions of Python are supported in each release of Numpy? I found an FAQ that mentioned 2.4 and 2.5, but since it didn't mention 2.6 or 2.7 (much less 3.1), I assume

Re: [Numpy-discussion] printoption to allow hexified floats?

2010-12-01 Thread Robert Kern
On Wed, Dec 1, 2010 at 13:18, Ken Basye kbas...@jhu.edu wrote: Hi Numpy folks,     When working with floats, I prefer to have exact string representations in doctests and other reference-based testing; I find it helps a lot to avoid chasing cross-platform differences that are really about the